Re: Patch to propagate GDB's knowledge of the executing state to frontend

[Tom Tromey <tromey at redhat dot com>]

Luis> Should frontends relying on MI information treat ^error specially and
Luis> not look for any *stopped records?

I don't know the answer to this.  I did find this though:

http://sourceware.org/bugzilla/show_bug.cgi?id=7778

I tend to think it would be cleanest if gdb were to emit a *stopped in
case of error -- but only if it previously emitted *running.  I don't
know how feasible this is.

Luis> The MI specification gives room for slightly different interpretations
Luis> unfortunately.

For me, the text for "*running" is pretty clear:

     The frontend should assume that no interaction with a
     running thread is possible after this notification is produced.

I'm curious where the text is that gives room for another approach.

Tom