MI *stopped versus silent breakpoint

Daniel Jacobowitz drow@false.org
Fri Feb 6 02:30:00 GMT 2009

On Thu, Feb 05, 2009 at 06:24:41PM -0500, Marc Khouzam wrote:
> In the scenario you mention, having a proper *stopped event for 
> silent bp would pretty much be unnoticed by the user thanks to the 
> *running event that immediately follows (the frontend would stop and 
> resume right away.)  Same situation for the reverse-finish situation.

Is any FE likely to get upset that threads resume without its
"permission"?  You'd probably see the *stopped, try to get a stack
frame, and then get a *running instead...

Daniel Jacobowitz

More information about the Gdb mailing list