From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: chanskw@ca.ibm.com, gdb@sources.redhat.com
Subject: Re: Questions about GDB-MI Interface
Date: Thu, 25 Apr 2002 07:05:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020425180255.22413F-100000@is> (raw)
In-Reply-To: <3CC80775.8070803@cygnus.com>
On Thu, 25 Apr 2002, Andrew Cagney wrote:
> It was added with much hesitation because there was real concern that
> once a vaguely looking console mechanism was added, people would try to
> use it instead of investing the time and resources needed to address the
> problem of implementing a real console interface.
What was envisioned as a solution for the problem at hand, namely, that
any decent front-end to GDB must allow the user to type CLI commands?
next prev parent reply other threads:[~2002-04-25 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 13:01 chanskw
2002-04-24 21:55 ` Eli Zaretskii
2002-04-25 6:41 ` Andrew Cagney
2002-04-25 7:05 ` Eli Zaretskii [this message]
2002-04-25 7:41 ` Andrew Cagney
2002-04-25 11:59 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 9:25 chanskw
2002-04-23 10:36 chanskw
2002-04-24 7:55 ` Andrew Cagney
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=Pine.SUN.3.91.1020425180255.22413F-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=chanskw@ca.ibm.com \
--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