Re: [RFC] -mi-level command

[Andrew Cagney <ac131313@redhat.com>]

>> Should it also include the gdb version string?
> 
> 
> It is already covered by:
> 	-gdb-version

Doh!

>> Should it indicate the range of supported MI versions?
>> (what ever is useful).
> 
> 
> I think what you are referring is a set command like
> 
> -mi-set-level "mi2"
> 
> In this case, I am only interested in knowing the mi protocol version.

Ok.

>> 'gdb -i=mi2' should get you back to something that was released in 5.3. 
>>   "mi3" won't become official until GDB 6 is released, however, for it 
>> it return "2" would be wrong.
>> 
> 
> 
> Well the problem is that the function mi_version() is returning "3"
> How can I, reliably, get the MI version beeing use?

Use a GDB from a released branch (hope I remember to do the next one 
correctly).  At that point -gdb-version should return something 
meaningful, and -mi-version will be considered frozen.

The gdb on the mainline gets its mi version rolled as soon as something 
incompatible gets changed.  So while the last release reports "2", the 
mainline reports the work-in-progress "3".

>> It will need documentation and a testcase.
>> 
> 
> 
> Agreed, will do, if the new command is accepted.
> 
> BTW: seems to have some confusion with "MI level" and "MI version"
> 
> Should the command name be :
> -mi-level
> or
> -mi-version

Argh.

I suspect -mi-version is better.  There are potential incompatibilities 
between the diferent versions.

Andrew