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, 24 Sep 2009 18:31:00 -0000	[thread overview]
Message-ID: <m3bpl0dwkf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <19131.969.240479.323260@totara.tehura.co.nz> (Nick Roberts's 	message of "Thu, 24 Sep 2009 17:29:45 +1200")

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

Nick, sorry about the double reply.  The copy of your message that I
received was CCd to gdb-patches@redhat.com... either you resent it (?)
or there is some bad address mangling going on somewhere.  (If you did
not resend it, let me know, because I'd like to try to track down the
problem.)

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

Nick> How does that work?

GDB has code in it to automatically find and read a .py file when a new
objfile is created.  On Fedora, we install such a file that loads the
libstdc++ printers when libstdc++.so is used by the inferior.

See (info "(gdb)Auto-loading") for the details.

Tom


      reply	other threads:[~2009-09-24 18:31 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
2009-09-24  5:29       ` Nick Roberts
2009-09-24 18:31         ` Tom Tromey [this message]

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=m3bpl0dwkf.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