Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 01:35:00 -0000	[thread overview]
Message-ID: <m3iqg0izeh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <19103.5356.263602.590270@totara.tehura.co.nz> (Nick Roberts's 	message of "Thu, 3 Sep 2009 12:59:24 +1200")

>>>>> "Nick" == Nick Roberts <nickrob@snap.net.nz> writes:

Nick> No problem, it was only a small patch.  Were you aware that
Nick> changed values aren't reported?  Does your patch fix the problems
Nick> that I mentioned?

Yeah, it should fix those problems.

Tom> GCC svn trunk has pretty-printers for basically everything in
Tom> libstdc++ :-)

Nick> Cool!  Will they be distributed as part of the libstdc++ package
Nick> files?  i.e. with future GNU/Linux distributions

Yes, they are installed in a way that lets them auto-activate, if the
distro configures everything properly.  We're already doing this in
Fedora 11.

Tom> I'd like to write printers for some other programs (gdb, or gcc, or
Tom> python, or emacs) but haven't found the time ...

Nick> I'm not sure what you mean.  I was thinking of writing lisp code
Nick> so that Emacs can parse the output of the pretty printers like the
Nick> ones you describe above.

At least gcc, emacs, and python all have their own complicated .gdbinit
files with commands to help print data structures more nicely.  I think
it would be nice to convert these to use the pretty-printer
infrastructure.  This provides a couple concrete advantages: it works
better with MI, and it works in stack traces.

Tom


  reply	other threads:[~2009-09-03  1:35 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
2009-09-03  0:59   ` Nick Roberts
2009-09-03  1:35     ` Tom Tromey [this message]
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=m3iqg0izeh.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