public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Fri, 08 Oct 2004 07:17:00 -0000	[thread overview]
Message-ID: <20041008023243.GA15320@white> (raw)
In-Reply-To: <20041006212652.GB13271@white>

On Wed, Oct 06, 2004 at 05:26:52PM -0400, Bob Rossi wrote:
> On Wed, Oct 06, 2004 at 04:12:32PM -0400, Andrew Cagney wrote:
> > Bob, what's your overall objective here?  Perhaphs our lack of 
> > appreciation of your overriding goals is the reason that some (at least 
> > I) are feeling somewhat puzzled and confused.

Andrew, I would really like some closure on these issues, and since you
are the only MI maintainer that responds publically, I figured you could
help me out here.

I asked this question a week ago and still do not know the answer. This
is some information I must know in order to figure out how my front end
will deal with different versions of GDB, including CVS snapshots.

When I use "support" below, I mainly mean tested in the testsuite and
considered stable. 

>    * 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.
A backwards incompatible change would bump the revision.

>    * 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?

A backwards incompatible change at this point would bump the revision at
first, but every other backwards compatible revision would not bump the
revision until the release, which then the protocol becomes tested and
stable.

>    * I would like to make sure that development protocols are never used
>      by my front end and that I can figure out all of the officially 
>      supported MI protocols that a given GDB supports.

This issue can have different solutions if we know the answer to the
questions above.

Thanks,
Bob Rossi

  parent reply	other threads:[~2004-10-08  2:32 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 [this message]
2004-10-08 12:41     ` Eli Zaretskii
2004-10-08 13:23       ` Bob Rossi
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=20041008023243.GA15320@white \
    --to=bob@brasko.net \
    --cc=cagney@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).