Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Registering pretty-printers
Date: Sun, 07 Jun 2009 23:11:00 -0000	[thread overview]
Message-ID: <200906080310.58102.vladimir@codesourcery.com> (raw)


Hello,
I have a concern about the way Python pretty-printers seem to work now.
To register a pretty-printer, one is supposed to do this
(according to http://permalink.gmane.org/gmane.comp.debugging.archer/1352)

	import sys
	sys.path.insert(0, 'XXX')
	from libstdcxx.v6.printers import register_libstdcxx_printers
	register_libstdcxx_printers (None)

This seem to contain quite a lot of information that is specific
for given pretty printer -- like the package name, and the name
of function to register pretty-printers. Some other project
might have package named boost and function called register_boost_printers,
and some other package might use something else. As result, it is not
possible to IDE user to just point at directory and have pretty-printers
loaded. Can we maybe require that the __init__ module does registration?

I am not quite sure how to avoid specifying this random (for user)
libstdcxx.v6 part -- any ideas?

- Volodya



             reply	other threads:[~2009-06-07 23:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 23:11 Vladimir Prus [this message]
2009-06-10 19:25 ` Tom Tromey
2009-06-11  8:29   ` Vladimir Prus
2009-06-11 17:14     ` Paul Pluzhnikov
2009-06-12  0:52       ` Daniel Jacobowitz
2009-06-12  7:20         ` Vladimir Prus
2009-06-12 16:43         ` Doug Evans
2009-06-12 16:51           ` Daniel Jacobowitz
2009-06-12 17:12             ` Doug Evans
2009-06-12 17:06         ` Tom Tromey
2009-06-12 17:36     ` Tom Tromey
2009-06-12 17:43       ` Vladimir Prus
2009-06-15 20:23         ` Tom Tromey
2009-06-26 20:37           ` Tom Tromey
2009-06-27 10:16             ` Vladimir Prus

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=200906080310.58102.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb@sources.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