[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#165892: libc6-dbg seems to have no debugging infos in libc-2.3.1.so



Package: libc6-dbg
Version: 2.3.1-3
Severity: important

As the title says, it seems that the /usr/lib/debug/libc-2.3.1.so file installed by the libc6-dbg package
does not contain debugging infos...
Am I right, or the xxx-dbg packages are intended to be used in conjunction with the source packages, in order to avoid developpers compiling manually the libraries for chich they require debug infos ?
(Which works fairly well with the X11 libs, for example)

More detailed description and samples follow.

Bye,
--
Steve


nm -l /usr/lib/debug/libc-2.3.1.so | grep /
  does not report any source file name

However it seems that stripping it manually remove some debug infos

$ cd /tmp
$ cp /usr/lib/debug/libc-2.3.1.so .
$ cp libc-2.3.1.so libc-2.3.1-stripped.so
$ strip libc-2.3.1-stripped.so
$ ls -l libc*
-rw-r--r--    1 users     1158464 Oct 22 15:11 libc-2.3.1-stripped.so
-rw-r--r--    1 users     1376204 Oct 22 15:11 libc-2.3.1.so

but I don't think that 200k of debug infos is enough for a libc....

Another sample, using gdb on a prog :

$ export LD_LIBRARY_PATH=/usr/lib/debug
$ ldd ./valgui
...
      libc.so.6 => /usr/lib/debug/libc.so.6 (0x40c1b000)
...

$ gdb ./valgui
GNU gdb 2002-08-18-cvs
...
(gdb) b __libc_start_main
Breakpoint 1 at 0x8057f48
(gdb) r
Starting program: /home/steve/src/cvs/valgui/valgui/src/valgui
Breakpoint 1, 0x40c3091e in __libc_start_main () from /usr/lib/debug/libc.so.6
(gdb) bt
#0  0x40c3091e in __libc_start_main () from /usr/lib/debug/libc.so.6






Reply to: