https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Jeffrey Walton from comment #7) > > Thanks again Andrew. > > We have exception handlers for both CryptoPP::Exception& and std::exception& > starting for main() around > https://github.com/weidai11/cryptopp/blob/master/test.cpp#L442 . However, we > should not hit either of them. When they trigger there's a problem that > needs to be fixed. > > The code in question tests for good and bad digital signatures. It should > catch a SignatureVerificationFailed exception on occasion and this is > expected. But it should catch closer to the the actual test (and not in main > or Test::scoped_main). Not to mention 'catch throw' is not catching anything > under gdb. > > Is there something we should be doing differently? Try putting a breakpoint on the following functions: _Unwind_RaiseException _Unwind_ForcedUnwind _Unwind_Resume _Unwind_Resume_or_Rethrow _Unwind_DeleteException besides _Unwind_Resume which will be hit at least once since the backtrace shows it was hit, what is the backtrace for these breapoints?
