MI *stopped versus silent breakpoint

["Marc Khouzam" <marc.khouzam@ericsson.com>]

Hi,

I just found out that a breakpoint can be made silent, in which case
there
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
resumed
automatically, and then a single-step is done.

In CLI, it makes it look like the inferior stopped only once, instead of
twice.

In MI though, with the *stopped events, we do get an empty
*stopped for the silent breakpoint.  So I see two *stopped events
consecutively.

I wondered if a silent breakpoint should in fact generate a *stopped
event
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
*stopped.
I stilled wondered about GDB though.

Marc