From: Stefan Weyergraf <stefan@weyergraf.de>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] implements MI "-file-list-exec-sections" (updated)
Date: Thu, 22 Apr 2004 23:31:00 -0000 [thread overview]
Message-ID: <200404230131.26261.stefan@weyergraf.de> (raw)
In-Reply-To: <20040422112230.GA7237@white>
> > Resubmitting updated (against current CVS) patch. Includes changes to
> > GDB/MI and docs. No test case yet.
> > 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)
The problem here is that:
1. I have converted the CLI output system for "info file" (*_files_info()) to
use ui_out. The MI uses the same procedure (target_info()) to process
"-file-list-exec-sections" (but a different ui_out instance)
2. "info file" deals with targets
3. targets have short (well machine readable) and long (well human readable,
localizable???) names
4. all fields provided in MI output end up in CLI output (that's the way
ui_out works)
5. it is desirable to have short names in MI output but short names are
currently not part of the CLI output.
>
> 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.
I don't think GDB development should be limited by keeping some CLI-standard
output. And GDB/MI and not GDB/CLI was made for front-ends after all. In a
perfect world...
Stefan
next prev parent reply other threads:[~2004-04-22 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 21:56 Stefan Weyergraf
2004-04-22 22:22 ` Bob Rossi
2004-04-22 23:31 ` Stefan Weyergraf [this message]
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
2004-04-30 21:54 Nick Roberts
2004-05-01 4:09 ` Bob Rossi
2004-05-01 12:08 ` Nick Roberts
2004-05-02 13:25 ` Bob Rossi
2004-05-07 1:19 ` 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=200404230131.26261.stefan@weyergraf.de \
--to=stefan@weyergraf.de \
--cc=gdb-patches@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