Re: [RFA] gdb-events.sh: selected-frame-level-changed event

[Andrew Cagney <ac131313 at ges dot redhat dot com>]

> On Sun, 25 Aug 2002, Andrew Cagney wrote:
>
>
> > Ok.
>
> Committed.

BTW, like any MI change, documentation and a testcase are also needed.

> > Any thoughts on how selected-thread events will be handled?  They also 
> > change the selected-fraome.
>
> I think that like many events, selected-thread change events imply that a 
> whole bunch of things have changed, too. For example, a target-stop event 
> (which we don't really issue as an event like the rest, but it is really 
> just an event), automatically implies that the selected frame, thread, and 
> other things have changed, yet we do not issue events for all of these. I 
> believe that the selected-thread event is the same.
GDB doesn't issue a target-stop event because it isn't possible to go 
back to GDB and ask it why it stopped.  The stop message is generated on 
the fly --- known bug in current implementation :-(

> In any case, I'm sure that we've done things wrong. In fact, I'd be 
> willing to bet that we have. But one small step forward is better than 
> none. We can always address issues as they appear, which is one of the 
> nice things about the event mechanisms: GDB itself doesn't use them! They 
> are UI-specific and quite isolated. :-)
We need to be careful though.  Otherwize GDB will be locked into 
supporting something broken for the next N years :-(


Andrew