Yann Dirson wrote: > > Correction: it works now (probably a compilation option that wasn't > used at the time). > > Problem: it's really a mmap image (thus works only for executables, > not libs), and includes the libs symbols: >
aha, but shared libs are executable files, so I succeeded building a shared lib with debug symbols (just ar -x and cc -shared) and then I gdb -batch -nx -mapped -readnow sharlib it builds sharlib.syms that gdb can load with -s. The problem is that gdb refuses to debug a shared lib, maybe needs some flag. But the real problem is that the sizes are ... unmanageable the shared lib is half the size of the static one, while the .syms file is double! -rw-r--r-- 1 2242044 Dec 13 19:20 libdb2.a -rwxr-xr-x 1 1129332 Dec 13 19:18 libdb2.so -rw-r--r-- 1 5246976 Dec 15 13:26 libdb2.so.syms A quick scan of gdb info let me suppose that debugging of shared libs is not easy under Intel platforms. So I loose all interest in using .syms files instead of unstripped static libs. Fabrizio -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | Pluto Leader - Debian Developer & Happy Debian 1.3.1 User - vi-holic | 6F7267F5 fingerprint 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
