#3048: libstdc++.so.6.0.14-gdb.py installed in the wrong place
-----------------------------------------+----------------------------------
Reporter: bdubbs@… | Owner: bdubbs@…
Type: enhancement | Status: reopened
Priority: normal | Milestone: 7.2
Component: Book | Version: SVN
Severity: normal | Resolution:
Keywords: |
-----------------------------------------+----------------------------------
Comment(by bryan@…):
Replying to [comment:6 bdubbs@…]:
> Looking at the gdb documentation, it looks like it should be
>
> /usr/share/gdb/auto-load/<full path + name>-gdb.py
The gdb source agrees, if I make an assumption that the standard "source
search path" includes /usr/share/gdb/auto-load, FWIW.
However, the gdb source also shows that there's support for autoloading
these python extensions from a ".debug_gdb_scripts" ELF section in the
shared object. Does libstdc++ have one of these? (What does "readelf -x
.debug_gdb_scripts libstdc++.so.blah" dump for it? The first byte in the
section is 1, and the next sequence of bytes is a zero-terminated script
name; multiple scripts can be in a single section.)
I doubt we can change that section, but that might be a way to figure out
what name gdb will attempt to look for first.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/3048#comment:7>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
