"break into debugger" command line option doesn't work for unexpected exceptions

[vadz]

It's unexpected that unexpected exceptions in the tests don't break into the debugger. It's also inconvenient as debugging them is more difficult because of this, especially if you have other exceptions which are expected and handled.

I think this should be changed and, as usual, would be ready to make a PR for this if you agree, please let me know if you do, TIA!

Just for the record, here is the minimal test allowing to reproduce this:

#define CATCH_CONFIG_MAIN
#include <catch.hpp>

TEST_CASE("exception") { throw "nobody expects the Spanish inquisition"; }

If you compile and run it under gdb:

% g++ tst.cpp && gdb --args ./a.out -b
Reading symbols from ./a.out...done.
(gdb) r
Starting program: /.../a.out -b

\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.out is a Catch v1.3.3 host application.
Run with -? for options

-------------------------------------------------------------------------------
exception
-------------------------------------------------------------------------------
tst.cpp:4
...............................................................................

tst.cpp:4: FAILED:
due to unexpected exception with message:
  nobody expects the Spanish inquisition

===============================================================================
test cases: 1 | 1 failed
assertions: 1 | 1 failed

[Inferior 1 (process 22104) exited with code 01]

the expected SIGTRAP doesn't happen.

[lorenzhs]

Have you seen #418?

[vadz]

No, sorry, I hadn't. I agree that it's the same thing and will close this one, thanks.