This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: MI documentation
- From: Fabian Cenedese <Cenedese at indel dot ch>
- To: gdb at sources dot redhat dot com
- Date: Thu, 30 Sep 2004 08:34:58 +0200
- Subject: Re: MI documentation
>I was wondering how GDB documents the different versions of MI. For
>instance, how do you know what MI commands are available with
>specific versions of MI? What fields do the commands output for
>specific versions? What asynchronous notifications are possibly outputted
>with MI version 1,2,3?
I think the way to go is the probing of each needed command. If it's
available the frontend can use it, if not the frontend needs a fallback.
This is done e.g. in the remote protocol. If the vCont command is not
implemented the simpler s and c commands are used. This is somehow
similar to the MI. If the tagged commands are not implemented (older
gdb) the untagged commands can be used, even with less reliability.
So THE ONE version number is not really usefull as you also stated
earlier. But I don't know how a frontend can _ask_ what async
notifications could come.
bye Fabi