This is the mail archive of the
mailing list for the GDB project.
MI *stopped versus silent breakpoint
- From: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- To: <gdb at sourceware dot org>
- Date: Wed, 21 Jan 2009 10:41:01 -0500
- Subject: MI *stopped versus silent breakpoint
I just found out that a breakpoint can be made silent, in which case
is no breakpoint output when it is hit. When doing a reverse-finish
operation, a silent breakpoint is used, and when hit the inferior is
automatically, and then a single-step is done.
In CLI, it makes it look like the inferior stopped only once, instead of
In MI though, with the *stopped events, we do get an empty
*stopped for the silent breakpoint. So I see two *stopped events
I wondered if a silent breakpoint should in fact generate a *stopped
or not? For a frontend, it can be confusing to see two stopped events.
FYI, what I did for DSF-GDB and reverse debugging, is to ignore empty
I stilled wondered about GDB though.