Registering pretty-printers
Daniel Jacobowitz
drow@false.org
Fri Jun 12 00:52:00 GMT 2009
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
More information about the Gdb
mailing list