Is there any nice way to achive more detailed information about uncaught custome exceptions in a Boost unit test. I understand that it is possible to register custom exceptions, but that is quite some work when using several 3rd party libraries. I would be even hapier if it was possible to get some stacktrace, or linenumber (within the Boost test file) on which the exception occured. Jarl
Jarl Friis
Is there any nice way to achive more detailed information about uncaught custome exceptions in a Boost unit test.
I understand that it is possible to register custom exceptions, but that is quite some work when using several 3rd party libraries.
I would be even hapier if it was possible to get some stacktrace, or linenumber (within the Boost test file) on which the exception occured.
This work is frozen for now. I hope to return later this year. Gennadiy
participants (2)
-
Gennadiy Rozental -
Jarl Friis