This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: probing GDB for MI versions
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: "'Bob Rossi'" <bob at brasko dot net>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 08 Oct 2004 10:36:45 +0200
- Subject: Re: probing GDB for MI versions
- References: <20041007145511.GA14573@white> <200410071614.MAA19648@smtp.ott.qnx.com> <20041007224230.GA15177@white>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 7 Oct 2004 18:42:30 -0400
> From: 'Bob Rossi' <bob@brasko.net>
> Cc: Dave Korn <dk@artimi.com>, gdb@sources.redhat.com
>
> * Have GDB output it's last stable version of MI as the first thing
> it outputs (subset of case above)
Will this solution be satisfactory for you? That is, when invoked
with the -interpreter=mi<N> command-line switch, GDB will print the
last stable version of the MI protocol it supports. This is actually
the way many protocol negotiations start, and I don't see why we
shouldn't behave the same.
Note that a front end which wants to support older GDB versions will
need to have a database of MI versions referenced by GDB versions,
because the old GDB versions will not print the MI version.
Are there any disadvantages to this solution?