Catching exceptions in debug mode makes it impossible to use gdb or gdb-python
Created by: siebenkopf
When using the
BOB_CATCH_... macros, any C++ exception in the C++ code (and in the binding code) is caught and reported as a python exception:
While this should be the desired practice in release mode (i.e., the python program is not stopped by the C++ exception), in debug mode this might be a bad idea, as debuggers like
gdb (or more specifically,
gdb-python) do not stop at the place, where the exception happens.
So, do you think it is a good idea to disable the exception handling by
BOB_CATCH_... in debug mode, i.e., when the
BOB_DEBUG flag is set?