debug info packages for F8 & libc

[gshcherb]

Hello!

I have installed latest zero debugger on my F8 (1.12.105) and debug
info packages for libc and ld. The appropriate info located in /usr/
lib/debug as it should be. For some reason zero do not show me the
sources of binaries included in those packages - only rough gas code.

I also tried to specify custom location to ZERO_DEBUG_SYMBOLS_DIR env
variable, but had not luck.
Here stated that ZeroBUGS should understand and pick up needed
information transparently.

What should be tuned to force zero show debug info for standard
packages?

Thanks & Regards,

[gshcherb]

Stated here :)
http://the-free-meme.blogspot.com/2007/09/debugger-tip-1-leaner-binaries.html

[cristiv]

Assuming that:
1) you installed the sources that go with the respective debug
packages and
2) you linked your code with the debug packages

then one thing I can think of is that the source code paths as
recorded inside the debug info may not be the same with the location
on your machine.

You may try this using ZERO_PATH_MAP as described here:
http://the-free-meme.blogspot.com/2008/03/watch-expressions.html

Best regards,
Cristian

PS I hope to update the FC8 build later tonight (fixing some small
glitches in the UI).

[gshcherb]

Here is my info:

rpm -qa | grep glibc
glibc-debuginfo-common-2.7.90-7
glibc-devel-2.7.90-7
glibc-common-2.7.90-7
glibc-utils-2.7.90-7
glibc-2.7.90-7
glibc-headers-2.7.90-7
glibc-debuginfo-2.7.90-7


ls -l /lib/libc*
-rwxr-xr-x 1 root root 1786836 2008-02-16 22:20 /lib/libc-2.7.90.so
lrwxrwxrwx 1 root root 14 2008-02-29 18:37 /lib/libc.so.6 ->
libc-2.7.90.so
*cut*

objdump -s libc-2.7.90.so | grep -A 2 debuglink
Contents of section .gnu_debuglink:
0000 6c696263 2d322e37 2e39302e 736f2e64 libc-2.7.90.so.d
0010 65627567 00000000 789f585a ebug....x.XZ

> You may try this using ZERO_PATH_MAP as described here:http://the-free-meme.blogspot.com/2008/03/watch-expressions.html

Tried to do:

export ZERO_PATH_MAP=/usr/src/debug/glibc-20080216T1726

ls -l /usr/src/debug
drwxr-xr-x 58 root root 4096 2008-02-29 18:28 glibc-20080216T1726

ls -l /usr/lib/debug/lib/libc*
-rwxr-xr-x 1 root root 6112240 2008-02-16 22:20 /usr/lib/debug/lib/
libc-2.7.90.so.debug
-rwxr-xr-x 1 root root 60920 2008-02-16 22:20 /usr/lib/debug/lib/
libcidn-2.7.90.so.debug
lrwxrwxrwx 1 root root 23 2008-02-29 18:28 /usr/lib/debug/lib/
libcidn.so.1.debug -> libcidn-2.7.90.so.debug
-rwxr-xr-x 1 root root 65480 2008-02-16 22:20 /usr/lib/debug/lib/
libcrypt-2.7.90.so.debug
lrwxrwxrwx 1 root root 24 2008-02-29 18:28 /usr/lib/debug/lib/
libcrypt.so.1.debug -> libcrypt-2.7.90.so.debug
lrwxrwxrwx 1 root root 20 2008-02-29 18:28 /usr/lib/debug/lib/
libc.so.6.debug -> libc-2.7.90.so.debug


env | grep ZERO
ZERO_PATH_MAP=/usr/src/debug/glibc-20080216T1726
ZERO_CACHE_SYMBOLS=true
ZERO_DEBUG_SYMBOLS_DIR=/usr/lib/debug
ZERO_LINE_NEAREST_MATCH=false
ZERO_USE_FRAME_HANDLERS=true

If you have time and willing please advise.

Thanks & Regards,

[cristiv]

For the benefit of other users reading this thread:

After working on this issue off line with gshcherb I found a bug in
the ZeroBUGS plugin that deals with DWARF debug information;

the bug was since fixed in builds for Ubuntu (i386, x86_64), and
Fedora 7 and 8 (i386).

Cristian