From: Tom Tromey <tromey@redhat.com>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] varobj.c: Report changed values that use a pretty-printer
Date: Thu, 03 Sep 2009 00:08:00 -0000 [thread overview]
Message-ID: <m3y6owj3eo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <19103.1108.215005.684662@totara.tehura.co.nz> (Nick Roberts's message of "Thu, 3 Sep 2009 11:48:36 +1200")
>>>>> "Nick" == Nick Roberts <nickrob@snap.net.nz> writes:
Nick> I've had a play with pretty printing in MI and it looks really neat. I've
Nick> got Emacs to display map objects as described on Trom Tromey's page:
Nick> http://tromey.com/blog/?p=546
Nick> There have been a few problems, notably changed values don't seem
Nick> to get reported by -var-update. The patch below seems to fix
Nick> this.
Oops, bad timing ... I have a big patch to redo all this code, as
discussed on the gdb list and the archer list. It is on the
archer-tromey-python branch, but I plan to push it to CVS as soon as
Volodya declares it ready (and as soon as I tidy up the documentation,
my task for tomorrow).
Nick> The scope of this work seems enormous as it opens the possiblity
Nick> of formatting the watch expressions of all STL containers (as,
Nick> ISTR, is already done in Totalview). Of course the amount of work
Nick> it entails is probably enormous too and the problem, as always, is
Nick> finding someone to do it.
GCC svn trunk has pretty-printers for basically everything in libstdc++ :-)
I'd like to write printers for some other programs (gdb, or gcc, or
python, or emacs) but haven't found the time ...
Tom
next prev parent reply other threads:[~2009-09-03 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:48 Nick Roberts
2009-09-03 0:08 ` Tom Tromey [this message]
2009-09-03 0:59 ` Nick Roberts
2009-09-03 1:35 ` Tom Tromey
2009-09-24 5:29 ` Nick Roberts
2009-09-24 18:31 ` Tom Tromey
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=m3y6owj3eo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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