From: Bob Rossi <bob@brasko.net>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: Andrew Cagney <cagney@gnu.org>,
Stefan Weyergraf <stefan@weyergraf.de>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] implements MI "-file-list-exec-sections" (updated)
Date: Sat, 01 May 2004 04:09:00 -0000 [thread overview]
Message-ID: <20040501040929.GB17480@white> (raw)
In-Reply-To: <16530.51947.983270.138336@nick.uklinux.net>
On Fri, Apr 30, 2004 at 10:53:47PM +0100, Nick Roberts wrote:
>
> > > > Maybe it's worth mentioning, that GDB/CLI output for "info file" changes
> > > > with this patch which will probably break programs that parse this. (I
> > > > don't think such programs exist)
>
> > > I get the feeling that changing the CLI output of "info file" is a bad
> > > idea. My hunch is that some front ends to GDB are calling that function.
>
> > One motivation of MI was to free us of this concern, we have to start
> > somewhere. I should look at this in the morning.
>
> For information only, please note that gdb-ui.el (CVS Emacs) currently uses
> CLI output from the following commands:
>
> info source
> info breakpoints
> where
> info threads
> info registers
> info locals
> disassemble
> info frame
>
> I plan to put a more basic version that uses GDB/MI into CVS as soon as Emacs
> is released, whenever that might be. Andrew, if you are planning to change CLI
> output could you please convey this to Richard Stallman, so that there can be
> some co-ordination of schedule between GDB and Emacs.
I think everyone agrees, changing the CLI would be the worst possible
thing GDB could do. What other options are there?
For some unfortunate reason, every front end would break in some subtle
way if the output of the CLI was modified. In some way, it doesn't
really make sense to just coordinate GDB with Emacs and not every other
front end, right?
Bob Rossi
next prev parent reply other threads:[~2004-05-01 4:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 21:54 Nick Roberts
2004-05-01 4:09 ` Bob Rossi [this message]
2004-05-01 12:08 ` Nick Roberts
2004-05-02 13:25 ` Bob Rossi
2004-05-07 1:19 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 21:56 Stefan Weyergraf
2004-04-22 22:22 ` Bob Rossi
2004-04-22 23:31 ` Stefan Weyergraf
2004-04-28 21:51 ` Andrew Cagney
2004-05-07 1:20 ` Andrew Cagney
2004-05-06 22:07 ` Stefan Weyergraf
2004-05-12 20:14 ` 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=20040501040929.GB17480@white \
--to=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nick@nick.uklinux.net \
--cc=stefan@weyergraf.de \
/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