This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MI documentation


On Thu, Sep 30, 2004 at 08:34:58AM +0200, Fabian Cenedese wrote:
> 
> >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.

So that only answers what syncronous commands are avaiable with the
current version even thought the front end wouldn't know the version
number.

It still doesn't tell you the asyncronous commands like you mentioned or
the fields that are available for input commands or anything else that I
would need to know for certain versions.

I feel that knowing these things are a minimum requirement for having a
protocol between 2 processes.

Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]