From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: starting gdb/mi from FE
Date: Mon, 05 Jun 2006 19:59:00 -0000 [thread overview]
Message-ID: <20060605195930.GA31015@nevyn.them.org> (raw)
In-Reply-To: <20060605134517.GA25925@brasko.net>
On Mon, Jun 05, 2006 at 09:45:17AM -0400, Bob Rossi wrote:
> This will allow the FE to start GDB 1 time and to determine which
> version of the protocol GDB was compatible with. If you have multiple
> interpreter choices on the -i switch, then GDB will output the first
> line it writes as
> mi_protocol_version=miN
> where miN will be the version GDB is going to communicate with.
>
> This change is backwards compatible because users were not able in the
> past to have a comma separated list in the -i flag.
>
> How does this look?
We've discussed this at least twice in the past, haven't we? How about
a pointer to those past conversations; did they reach a conclusion, or
not - and if they did, was it this one?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-05 19:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 13:45 Bob Rossi
2006-06-05 19:56 ` Eli Zaretskii
2006-06-05 19:58 ` Bob Rossi
2006-06-05 20:23 ` Eli Zaretskii
2006-06-05 21:25 ` Daniel Jacobowitz
2006-06-05 21:28 ` Bob Rossi
2006-06-06 3:44 ` Eli Zaretskii
2006-06-05 19:59 ` Daniel Jacobowitz [this message]
2006-06-05 20:49 ` Bob Rossi
2006-06-06 0:55 Nick Roberts
2006-06-06 1:20 ` Daniel Jacobowitz
2006-06-06 1:56 ` Bob Rossi
2006-06-06 3:16 ` Daniel Jacobowitz
2006-06-06 2:03 ` Nick Roberts
2006-06-06 2:04 ` Bob Rossi
2006-06-06 17:22 ` Jim Ingham
2006-06-06 17:30 ` Daniel Jacobowitz
2006-06-06 17:41 ` Jim Ingham
2006-06-06 1:33 ` Bob Rossi
2006-06-06 1:56 ` Nick Roberts
2006-06-06 2:01 ` Bob Rossi
2006-06-06 2:30 ` Nick Roberts
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=20060605195930.GA31015@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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