Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Fri, 08 Oct 2004 13:23:00 -0000	[thread overview]
Message-ID: <20041008121321.GB15978@white> (raw)
In-Reply-To: <01c4ad2b$Blat.v2.2.2$f25b86a0@zahav.net.il>

On Fri, Oct 08, 2004 at 01:41:50PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 7 Oct 2004 22:32:43 -0400
> > From: Bob Rossi <bob@brasko.net>
> > 
> > >    * I would like to know what GDB's policy is in regards to supporting old
> > >      MI protocols.  ( I have received several opposing views on this )
> > 
> > A new way to phrase this would be, for a given release of GDB (not a CVS
> > snapshot), does that release support one MI protocol, or does it support
> > several MI protocols. The MI protocols need to be tested and stable.
> 
> The answer to this is that, although the latest stable MI version is
> probably the most stable version to rely upon, the old MI versions are
> also supported to the degree that there are tests in the test suite
> that exercise them.  For example, currently there are tests for mi1
> although the latest MI version is mi2.
> 
> Of course, bugs in MI versions other than the latest will probably not
> be corrected.

Right, I wouldn't expect them to be.

OK, Andrew gave me the exact opposite answer here. That is why I asked again
   http://sources.redhat.com/ml/gdb/2004-10/msg00177.html

maybe I'm wrong, and you guys are saying the same thing?

> > >    * I would like to ensure that my front end works well with snapshots
> > >      of GDB. I do not want to work with the MI development protocol, I
> > >      just want to work with the last officially supported protocol.
> > 
> > For CVS snapshots, does GDB only support (tested) the development MI
> > protocol? or does it support the last stable protocol? or does it
> > support multiple stable protocols?
> 
> Again, the answer is that the support guarantee is the same for the
> CVS versions: whatever the test suite exercises is supported to the
> same degree.

It is important to me that the CVS snapshots try to at least honor the
last major MI version before the version bump. Is this something
everyone thinks will be possible?

I do understand that old MI protocols could be dropped because of
maintenance issues. Would we go as far as dropping the last stable
protocol, this could potentially be a problem for me.

Thanks,
Bob Rossi


  reply	other threads:[~2004-10-08 12:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 20:13 Andrew Cagney
2004-10-06 22:36 ` Bob Rossi
2004-10-07  2:40   ` Andrew Cagney
2004-10-07 17:20     ` Bob Rossi
2004-10-07 20:50       ` Andrew Cagney
2004-10-07 22:42         ` Bob Rossi
2004-10-08  8:40           ` Fabian Cenedese
2004-10-08 13:17             ` Bob Rossi
2004-10-08  7:17   ` Bob Rossi
2004-10-08 12:41     ` Eli Zaretskii
2004-10-08 13:23       ` Bob Rossi [this message]
2004-10-08 13:42         ` Eli Zaretskii
2004-10-08 16:34         ` Daniel Jacobowitz
2004-10-08 16:28       ` Daniel Jacobowitz
2004-10-08 18:57         ` Eli Zaretskii
2004-10-09 11:14           ` Andrew Cagney
2004-10-10  4:06             ` Bob Rossi
2004-10-11  2:00               ` Bob Rossi
2004-10-11 14:12                 ` Andrew Cagney
2004-10-11 17:22                   ` Bob Rossi
2004-10-12 22:15                     ` Michael Chastain

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=20041008121321.GB15978@white \
    --to=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    /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