[pushed+RFC] C++ exception during command triggers stale cleanup internal-warning

Joel Brobecker brobecker@adacore.com
Tue May 22 14:49:00 GMT 2018


There was a small bug in Tom's patch that caused the execution
of the "catch assert" command to throw a C++ exception. I have
pushed the following patch to master as an obvious fix to the
immediate issue:

  [] fix "stale cleanup" internal-warning when using "catch assert"

But at the same time, this leads me to believe we may have a weakness
top.c::execute_command, which installs a cleanup, and "forgets" to
discard it when C++ exceptions are raised.

But maybe that's just the way it is, and we just want to make sure
we never let C+ exceptions get away from us? Thoughts on that?

Anyways, for now, the immediate issue is fixed.


More information about the Gdb-patches mailing list