This is the mail archive of the archer@sourceware.org mailing list for the Archer project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] Fix glitches with libstdc++ pretty printers


On Thu, 30 Oct 2008 01:32:22 +0100, Paul Pluzhnikov wrote:
> As you pointed out, this may break if e.g. libstdc++.so.5,
> libstdc++.so.6 and libfancy_container.so.1 are all in /lib, there
> is no separate debuginfo, and all 3 libraries "fight" for /lib/.gdb.py.
...
> The approach I am considering is to put python pretty printing
> code into ".gdb_py" section in the object file which implements
> the "guts" of a container, and for GDB to automatically python-source
> this section when the object is loaded.

I do not find it easily user-accessible, for checking how the pretty printers
work and possibly extending them etc.  I would fine native to load in this
order (matching current GDB find_separate_debug_file behavior):
/usr/lib/debug/.build-id/03/f06dc...293c0-gdb.py
/usr/lib64/libstdc++.so.6-gdb.py
/usr/lib64/.debug/libstdc++.so.6-gdb.py
/usr/lib/debug/usr/lib64/libstdc++.so.6-gdb.py


Regards,
Jan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]