[Bug breakpoints/16551] Execution stops when encountering a dprintf with an invalid string

["antoine.tremblay at ericsson dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16551

--- Comment #3 from Antoine Tremblay <antoine.tremblay at ericsson dot com> ---
After much thought and some discussion on the gdb ml...

There was a few options :

Having a generic *stopped,error="xxx" event : was ruled out due to the
complexity of making this generic in gdb... unfortuanately we can't update the
thread state properly in case of error because of implementation details see :
https://sourceware.org/ml/gdb-patches/2015-02/msg00701.html

Having an *error aync message : This seemed like a good idea but it would
impact all the calls to print_exception, to be mi aware and sync/async aware
too, it seems like a bad idea code wise to mix that code.

We're left with the option to treat messages that start with "&" as a signal to
let the frontend know it should refresh it state.

I think this is the best option now since it basically does what the *error
async message would do and it's already implemented cleanly in gdb.

Note that the "&" prefix is directly associated with a print to stderr in gdb,
so we can safely assume it's an error signal.

So opon receiving a message starting with & the front end would refresh it's
state..

Marc does that sounds like an option for eclipse ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.