Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] varobj.c: Report changed values that use a pretty-printer
Date: Thu, 24 Sep 2009 05:29:00 -0000	[thread overview]
Message-ID: <19131.969.240479.323260@totara.tehura.co.nz> (raw)
In-Reply-To: <m3iqg0izeh.fsf@fleche.redhat.com>

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

How does that work?  I can see that a front-end can get GDB to read the file
printers.py, if it is distributed with the libstdc++ package, using
"library-loaded" notification:

=library-loaded,id="/usr/lib/libstdc++.so.6",target-name="/usr/lib/libstdc++.so.6",host-name="/usr/lib/libstdc++.so.6",symbols-loaded="0"

Or do you mean that the build of GDB in Fedora 11 will recognise that
libstdc++ has been loaded and then automatically read in the file printers.py?


-- 
Nick                                           http://users.snap.net.nz/~nickrob


  reply	other threads:[~2009-09-24  5:29 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 [this message]
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=19131.969.240479.323260@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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