This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SIGTRAP or SIG32 when remote debugging threads


On Tue, Mar 23, 2004 at 05:55:45PM +0100, Lukas Heiniger wrote:
> (gdb) set solib-absolute-prefix /home/hynix/arm/arm-linux
> (gdb) set solib-absolute-prefix /home/hynix/arm/arm-linux
> (gdb) c
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x40088534 in ?? ()
> 
> (gdb) set solib-absolute-prefix /home/hynix/arm/arm-linux
> Reading symbols from /home/hynix/arm/arm-linux/lib/libm.so.6...done.
> Loaded symbols for /home/hynix/arm/arm-linux/lib/libm.so.6

This suggests that the dynamic linker breakpoint wasn't hit.  You may
want to use 'set debug remote 1' and 'set debug target 1' to try to
figure out where the breakpoint was set, and why it wasn't hit.

>   2 Thread 2049  0x400fa7b8 in tcsetattr (fd=1, optional_actions=1, 
> termios_p=0x0) at ../sysdeps/unix/sysv/linux/tcsetattr.c:92
>   1 Thread 1024  0x40088534 in __sigsuspend (set=0xbffffc6c) at ../sysdeps/
> unix/sysv/linux/sigsuspend.c:54

These are taken from the debug information; they're relative to the
objdir when your target glibc was built.  They don't necessarily refer
to on-disk files.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]