This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] gdb-events.sh: selected-frame-level-changed event
- From: Keith Seitz <keiths at redhat dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Mon, 26 Aug 2002 13:11:44 -0700 (PDT)
- Subject: Re: [RFA] gdb-events.sh: selected-frame-level-changed event
On Mon, 26 Aug 2002, Andrew Cagney wrote:
> BTW, like any MI change, documentation and a testcase are also needed.
It doesn't change MI. CVS head MI doesn't even use events. Right now,
the only official user is Insight (which reminds me, I have yet to check
in changes for Insight to deal with these new events!).
I have patches in the interpreter branch which will change MI to using
gdb-events, and I have the corresponding documentation there, as
well. Just waiting for review of interps.[ch] to get this all going.
> 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 :-(
Yeah, but it's close enough! :-)
> We need to be careful though. Otherwize GDB will be locked into
> supporting something broken for the next N years :-(
I think that we can be a little finnicky about this. While UIs written on
top of MI may like it if we never change anything for a very long time,
well, I don't think we need to feel that we have any obligation to carry
around legacy code like this. We've certainly never heard from anyone but
Apple (and I guess Mo is doing something with MI), and Apple is certainly
capable of dealing with these changes.
:-) Besides people will get little sympathy from me. Just look at the
history of how some of the most innocent gdb changes have completely
broken Insight! :-)
Seriously, though, I applaud your chivalry on this subject, but interfaces
develop and "libraries" change. We're no different than, eg. readline, and
how often have we updated gdb to use the latest readline?
Keith