[<<][davinci][>>][..]
Sat Jul 25 14:40:38 CEST 2009

debugging symbols

Wait.  Maybe I missed something: does gdb need debugging symbols to be
able to catch the pthread signals, or just linker symbols?

This[1] might be the reason.  Using the following command file some
errors disappear, but I'm still getting the SIG32:

set confirm off
set solib-absolute-prefix /opt/xc/osd2/rootfs/fs/
file test
target remote neuros:12345
break debug
continue


[New Thread 908]
BFD: /opt/xc/osd2/rootfs/fs/lib/ld-linux.so.3: warning: sh_link not set for section `.ARM.exidx'
BFD: /opt/xc/osd2/rootfs/fs/lib/ld-linux.so.3: warning: sh_link not set for section `.ARM.exidx'
BFD: /opt/debian-lenny-i386/opt/xc/osd2/rootfs/default/lib/ld-linux.so.3: warning: sh_link not set for section `.ARM.exidx'
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
0x40000790 in ?? () from /opt/xc/osd2/rootfs/fs/lib/ld-linux.so.3
Breakpoint 1 at 0xb0bc: file test.c, line 264.
BFD: /opt/xc/osd2/rootfs/fs/lib/libpthread.so.0: warning: sh_link not set for section `.ARM.exidx'
BFD: /opt/xc/osd2/rootfs/fs/lib/libc.so.6: warning: sh_link not set for section `.ARM.exidx'
BFD: /opt/debian-lenny-i386/opt/xc/osd2/rootfs/default/lib/libpthread.so.0: warning: sh_link not set for section `.ARM.exidx'
BFD: /opt/debian-lenny-i386/opt/xc/osd2/rootfs/default/lib/libc.so.6: warning: sh_link not set for section `.ARM.exidx'

Program received signal SIG32, Real-time event 32.
0x40028e10 in ?? () from /opt/xc/osd2/rootfs/fs/lib/libpthread.so.0
(gdb) 

BUT.. with a couple of `continues' after this, it finally stops at the
breakpoint.  Let's simply add these to the startup script.  Yep.  It
starts fine now.


[1] http://stackoverflow.com/questions/84341/how-do-i-prepend-a-directory-the-library-path-when-loading-a-core-file-in-gdb-on



[Reply][About]
[<<][davinci][>>][..]