Re: MI handshaking

[Andrew Cagney <cagney@gnu.org>]

Alain Magloire wrote:
>>(as is obvious, 6.3 is effectively out, I'm draining the queue)
>>
>>Bob Rossi wrote:
>>
>>>BTW, here is an example of how it looks,
>>>
>>>$ ../../objdir3/gdb/gdb -i=mi
>>>mi_handshake={stable=mi2}
>>>~"GNU gdb 6.3.50_2004-11-04-cvs\n"
>>>~"Copyright 2004 Free Software Foundation, Inc.\n"
>>>~"GDB is free software, covered by the GNU General Public License, and you are\n"
>>>~"welcome to change it and/or distribute copies of it under certain conditions.\n"
>>>~"Type \"show copying\" to see the conditions.\n"
>>>~"There is absolutely no warranty for GDB.  Type \"show warranty\" for details.\n"
>>>~"This GDB was configured as \"i686-pc-linux-gnu\"."
>>>~"\n"
>>>(gdb)
>>>
>>>I can obviously change the syntax of the output if it is desired.
>>>There should probably be a '~' or something like that, any suggestions?
>>
>>Hmm, it's async (or unprompted), has the hypothetical potential for 
>>multiple values, and leaves us wondering which of those values it choose:
>>
>>*mi-handshake={version=mi2,stable=[mi2]}
>>
>>it should also appear after the copyright.
>>
>>Oh and testing ;-)
>>
>>Nick, Alain, comments?
>>
> 
> 
> Is it a good idea to make this an exec-async?  There is really no state changes.
> Printing it in the console-stream long with the
> gdb version should be enough.
> 
> But if async is desired, how about a notify-async instead.
> 
> =mi-handshake,versions=[mi1,mi2,mi3],stable=[mi2]

Yes, thanks for the correction with ``=''.   But not 
``versions=[mi1,mi2,mi3]'' that's too much and misleading information.

I think the objective here needs to be to provide as much information as 
possible about what version of GDB and MI is running.  Hence the:

	version="mi2"

(where hopefully VERSION version is a member of STABLE :-) although 
strictly speaking it should probably be:

	mi-version="mi2"

just in case there's later a gdb-version="6.3.50" etc.

Andrew

> As the doc is saying, notify-async contains supplementary information
> that the client should handle.
> 
> Note: did not look at the patch.