From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
Daniel Jacobowitz <drow@false.org>,
gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Mon, 11 Oct 2004 02:00:00 -0000 [thread overview]
Message-ID: <20041010181350.GA17779@white> (raw)
In-Reply-To: <20041008221026.GA16824@white>
On Fri, Oct 08, 2004 at 06:10:26PM -0400, Bob Rossi wrote:
> On Fri, Oct 08, 2004 at 05:35:22PM -0400, Andrew Cagney wrote:
> > @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes
> > @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, ,
> > The @sc{gdb/mi} Interface}) included since @var{GDBN} version 6.0. The
> > previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and
> > selected with @samp{--interpreter=mi1}, is deprecated. Earlier
> > @sc{gdb/mi} interfaces are no longer supported.
>
> This is basically what I need to know. I've asked several times and
> would very much appreciate an answer from the people that are capable of
> giving it. (The answer could be a simple yes or no)
>
> * Will GDB support at least one stable MI protocol for an official release?
> (This answer is obviously "yes", and does not have to be answered)
> * Will GDB support more than one stable MI protocols for an official release?
> * Will GDB support one stable MI protocol for a CVS snapshot?
> * Will GDB support more than one stable MI protocols for a CVS snapshot?
>
> BTW, The word "will" means that even if GDB supports only 1 official protocol currently,
> what about in the future?
>
> These questions are a prerequisite in determining how my front end will
> be able to interface with GDB. They are also a prerequisite to solving the
> MI handshaking problem.
Andrew, I know that you are a very busy person.
You have asked me several questions and I politely responded to you. I
would appreciate it if you could give me the same respect. Could you
please answer the questions I've asked you, not only from this Email but
from the rest of the ones in this thread?
From your lack of response to my questions (at least you respond), and the
*complete* lack of response from the other MI maintainers, I would say that
there is a problem with the maintenance of the MI section. The problem is
simply that I can not get general and simple answers about the MI code. I feel
that this should be something accomplishable ... do you?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2004-10-10 18: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
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 [this message]
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=20041010181350.GA17779@white \
--to=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=drow@false.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