Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Alain Magloire" <alain@qnx.com>
To: bob@brasko.net (Bob Rossi)
Cc: eliz@gnu.org (Eli Zaretskii), cagney@gnu.org (Andrew Cagney),
	alain@qnx.com, nick@nick.uklinux.net,
	gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Wed, 17 Nov 2004 16:05:00 -0000	[thread overview]
Message-ID: <200411171517.KAA28118@smtp.ott.qnx.com> (raw)
In-Reply-To: <20041113144830.GA296@white> from "Bob Rossi" at Nov 13, 2004 09:48:30 AM

> 
> On Sat, Nov 13, 2004 at 10:57:33AM +0200, Eli Zaretskii wrote:
> > > Date: Fri, 12 Nov 2004 17:57:30 -0500
> > > From: Andrew Cagney <cagney@gnu.org>
> > > Cc: Bob Rossi <bob@brasko.net>, Nick Roberts <nick@nick.uklinux.net>,
> > >         gdb-patches@sources.redhat.com
> > > 
> > > > =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 :-)
> > 
> > We've been through this discussion, and the only suggestion that
> > brought a consensus was to print all the supported MI versions, not
> > just one.  Let's not reopen that discussion again, even if the result
> > looks ``too much and misleading''.  (Why ``misleading'', btw?)
> 
> Yeah, anyways it doesn't really matter for now. GDB only supports one
> version, and I have a feeling it will stay that way for a long time.
> 

sigh ... sorry for being dense (hopefully this will not be a long thread)
but why are you keep on saying: "GDB only supports one version"
for example, I have gdb-6.1.x and I can start
# gdb -i mi1
# gdb -i mi2
# gdb -i mi3

that it is more then one version?


  reply	other threads:[~2004-11-17 16:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2004-11-12  9:54 Nick Roberts
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=200411171517.KAA28118@smtp.ott.qnx.com \
    --to=alain@qnx.com \
    --cc=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=eliz@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