This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: probing GDB for MI versions
- From: "Dave Korn" <dk at artimi dot com>
- To: "'Bob Rossi'" <bob at brasko dot net>,"'Eli Zaretskii'" <eliz at gnu dot org>,<gdb at sources dot redhat dot com>
- Date: Wed, 6 Oct 2004 18:41:05 +0100
- Subject: RE: probing GDB for MI versions
> -----Original Message-----
> From: Bob Rossi [mailto:bob@brasko.net]
> I want to make one thing clear, Eli's suggesting of making an
> MI command
> that returns the supported MI versions has one problem. We
> are adding a
> command to an MI protocol that can not be understood by a
> program that
> can speak a protocol. The program must,
>
> 1. Have a parser that understands the protocol it wants to speak
> (obvious and easy to get)
> 2. Have a parser that understands all future non invented protocols
> of the MI output syntax, and will be capable of parsing the current
> and future protocols to get the information it needs.
> (mostly not possible)
False inference.
> Will someone explain to me how they expect to write a parser
> capable of
> getting some information out of MI2, but prove to me that it will work
> with MI100.
Simple.
Any time anyone proposes changing the output format of the -mi-version
command, or removing it, we'll just say no. Fr'ex:
The -mi-version command will ALWAYS AND FOREVER output a string of the
format
"Highest supported MI version is XXXX"
where XXXX is an ASCII decimal integer. Any program can then read the
output from an invocation of gdb and simply discard everything up until it
finds that string, then parse the integer out.
cheers,
DaveK
--
Can't think of a witty .sigline today....