From: Andrew Cagney <ac131313@redhat.com>
To: Jim Ingham <jingham@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: Add fullname to breakpoint output
Date: Mon, 14 Apr 2003 04:14:00 -0000 [thread overview]
Message-ID: <3E9A3599.9080100@redhat.com> (raw)
In-Reply-To: <540DA746-6790-11D7-958C-000A277A8808@apple.com>
> Yes, this is a desirable goal. Have you thought about how to do this?
> The best way I can think of is to have a new ui_out that builds up an intermediate representation for results that is easy to access randomly - making up real lists & dictionaries from the ui_out_field_xxx and list & table stuff. Then we could banish ui_out_text & friends to the CLI commands to take the whole result, pull bits out in the order they expected, and annotate them with text, newlines, etc, in order to make a nice display.
>
> In practice, this will be gnarly to get right, but you could do it incrementally by getting the intermediate rep. ui_out working, then fix the CLI commands one by one by swapping in the new ui_out for those commands you had fixed, and using the old CLI one for the commands you hadn't gotten working...
I don't know that anything that complicated is needed. disasm.c worked
out pretty well.
Andrew
next prev parent reply other threads:[~2003-04-14 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1049485092.22026.ezmlm@sources.redhat.com>
2003-04-04 22:19 ` Jim Ingham
2003-04-05 17:28 ` Andrew Cagney
2003-04-05 17:59 ` Jim Ingham
2003-04-14 4:14 ` Andrew Cagney [this message]
2003-04-14 17:04 ` Jim Ingham
2003-04-04 19:38 Nick Roberts
2003-04-05 17:24 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 1:03 Bob Rossi
2003-04-03 1:26 Bob Rossi
2003-04-04 16:59 ` 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=3E9A3599.9080100@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.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