public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: MI and backwards compatibility
Date: Sat, 02 Oct 2004 17:06:00 -0000	[thread overview]
Message-ID: <01c4a89d$Blat.v2.2.2$ea76c2c0@zahav.net.il> (raw)
In-Reply-To: <20041002153815.GC5224@white> (message from Bob Rossi on Sat, 2 Oct 2004 11:38:15 -0400)

> Date: Sat, 2 Oct 2004 11:38:15 -0400
> From: Bob Rossi <bob@brasko.net>
> 
> Ping.

Well, one day without a response is hardly a good reason for a ping,
I'd say.  Especially during weekends.  I suggest to be slightly more
patient.

> I guess the main questions is, is the goal of GDB to support old
> versions of MI? For instance, if GDB is currently at MI3, will it
> support a front end that only knows MI2?

It should, and it does in most cases.

In those cases where the new MI version is too incompatible with the
previous one, we provide a suitable -interpreter=mi<N> switch to
alleviate the problem.

Thus, a frond-end which is known not to work with a new MI version
should use an explicit -interpreter=mi<N> switch when it invokes GDB.
The -version command-line switch is available to find out what GDB
version you are running with.

> If so, then I need the
> documentation for the MI2 interface if I want to make my front end work
> with that version of the protocol.

If needed, you can find the documentation of the MI2 interface in the
GDB documentation of the last version that supported MI2 as its
default MI interpreter.

However, I don't see why would you need to look up the old manual: the
previous versions of MI are maintained for those front ends that are
already written, so that they will not need anything beyond an
explicit mi<N> request to run with a version of GDB that was released
after the fron end.  Thus, a front end which is being developed
_after_ MI3 is released will not need to support MI2 in most cases,
right?

  reply	other threads:[~2004-10-02 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 14:25 Bob Rossi
2004-10-02 16:26 ` Bob Rossi
2004-10-02 17:06   ` Eli Zaretskii [this message]
2004-10-03  4:53     ` Bob Rossi
2004-10-03 15:02       ` Eli Zaretskii
2004-10-03 16:39         ` Bob Rossi
2004-10-02 16:28 ` Eli Zaretskii
2004-10-02 16:38   ` Bob Rossi
2004-10-02 17:24     ` Eli Zaretskii
2004-10-05 19:41 ` Andrew Cagney
2004-10-06  1:01   ` Daniel Jacobowitz

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='01c4a89d$Blat.v2.2.2$ea76c2c0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=bob@brasko.net \
    --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).