Re: GDB/MI snapshots between major release's

Bob Rossi
2004-10-06T01:03:37Z

On Tue, Oct 05, 2004 at 10:07:36AM -0400, Daniel Jacobowitz wrote:
> On Tue, Oct 05, 2004 at 11:14:44AM +0200, Eli Zaretskii wrote:
> > > Date: Mon, 4 Oct 2004 11:58:05 -0400
> > > From: Bob Rossi <bob@brasko.net>
> > > Cc: eliz@gnu.org, gdb@sources.redhat.com
> > >
> > > OK, this is good news. So basically, even thought the MI version is
> > > bumped it is still not official. Meaning, at that point, if I updated my
> > > front end to be compatible with the new MI protocol version, there could
> > > still be another incompatible change before the release. Meaning, I
> > > would have to wait for the release to get the use out of that new
> > > version. This is OK with me as long as,
> > >
> > > - I can have the --mi-protocols command line switch that tells me
> > > what version of GDB/MI protocol is officially supported.
> > >
> > > - This command line switch only has MI protocols added to it when the
> > > MI protocols become official ( for a release )
> >
> > We could do that, but I still think an MI command is a better vehicle
> > for such a feature.
>
> I think using a command line switch makes sense. You're going to have
> to restart GDB to change MI protocols anyway, so why force the user to
> go into MI?
>
> I also like the idea of listing non-MI (which right now means annotate)
> protocols in the same output.

Have we come to a resolution that a command like this is necessary?

I basically need it to query GDB to determine what MI versions it
officially supports.

It would satisfy my needs from GDB, but what about others?

Bob Rossi