Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
	tromey@redhat.com, 	gdb@sources.redhat.com
Subject: Re: Registering pretty-printers
Date: Fri, 12 Jun 2009 00:52:00 -0000	[thread overview]
Message-ID: <20090612005149.GA4987@caradoc.them.org> (raw)
In-Reply-To: <8ac60eac0906111014y67049cb9vb5048acf2939373b@mail.gmail.com>

On Thu, Jun 11, 2009 at 10:14:32AM -0700, Paul Pluzhnikov wrote:
> Perhaps my proposal for ".gdb_py" section here:
>   http://sourceware.org/ml/archer/2008-q4/msg00162.html
> deserves another look?
> 
> Maybe we don't even need a separate section; just a convention that any
> variable linked into executable, named "gdb_python_.*_source_me" and
> containing ASCII be "python sourced" by GDB?
> 
> The Boost code could declare:
> 
>   const char gdb_python_Boost_Array_source_me[] = "...python code here...";
> 
> in the header, and voila: GDB knows how to print boost::array.
> 
> This could also be easily distributed separately from the library, and
> the user will just have to link in gdb_boost_array_printer.c into his exe.

In my opinion, anything that increases the size of the executable is a
non-starter.  I don't think there's any reliable way to create a
non-allocatable section, and it would have other problems, like
duplicate elimination.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-06-12  0:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 23:11 Vladimir Prus
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 [this message]
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=20090612005149.GA4987@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ppluzhnikov@google.com \
    --cc=tromey@redhat.com \
    --cc=vladimir@codesourcery.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