Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Alain Magloire" <alain@qnx.com>
To: cagney@gnu.org (Andrew Cagney)
Cc: bob@brasko.net (Bob Rossi), alain@qnx.com (Alain Magloire),
	nick@nick.uklinux.net (Nick Roberts),
	gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Fri, 12 Nov 2004 03:44:00 -0000	[thread overview]
Message-ID: <200411120344.WAA11664@smtp.ott.qnx.com> (raw)
In-Reply-To: <4193CB73.6070402@gnu.org> from "Andrew Cagney" at Nov 11, 2004 03:28:35 PM

> 
> (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]

As the doc is saying, notify-async contains supplementary information
that the client should handle.

Note: did not look at the patch.


  reply	other threads:[~2004-11-12  3:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 19:57 Bob Rossi
2004-11-04 19:59 ` Bob Rossi
2004-11-11 20:30   ` Andrew Cagney
2004-11-12  3:44     ` Alain Magloire [this message]
2004-11-04 21:28 ` Eli Zaretskii
2004-11-05 16:39   ` Bob Rossi
2004-11-05 17:50     ` Eli Zaretskii
2004-11-05 22:12       ` Bob Rossi
2004-11-06 10:12         ` Eli Zaretskii
2004-11-08 14:49           ` Bob Rossi
2004-11-08 15:01             ` Eli Zaretskii
2004-11-12  9:54 Nick Roberts
     [not found] <200411120344.WAA24018@smtp.ott.qnx.com>
2004-11-12 22:59 ` Andrew Cagney
2004-11-13  9:01   ` Eli Zaretskii
2004-11-13 13:48     ` Bob Rossi
2004-11-17 16:05       ` Alain Magloire
2004-11-17 16:32         ` Bob Rossi
2004-11-18  1:35           ` Alain Magloire
     [not found]           ` <200411180135.UAA14730@smtp.ott.qnx.com>
2004-11-19 19:23             ` Bob Rossi
2005-01-05  1:36               ` Bob Rossi
2005-01-05  1:51                 ` Jim Ingham
2005-01-05  1:53                   ` Bob Rossi
2005-01-05  2:01                     ` Jim Ingham
2005-01-05  2:34                       ` Bob Rossi
2005-01-05  2:40                         ` Bob Rossi
2004-11-17 16:05     ` Alain Magloire
     [not found] <200411171514.KAA17361@smtp.ott.qnx.com>
2004-11-17 17:30 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200411120344.WAA11664@smtp.ott.qnx.com \
    --to=alain@qnx.com \
    --cc=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox