From: Daniel Jacobowitz <drow@false.org>
To: Lukas Heiniger <lukas.heiniger@fela.ch>
Cc: gdb@sources.redhat.com
Subject: Re: SIGTRAP or SIG32 when remote debugging threads
Date: Tue, 23 Mar 2004 20:41:00 -0000 [thread overview]
Message-ID: <20040323191337.GA28050@nevyn.them.org> (raw)
In-Reply-To: <200403231755.46001.lukas.heiniger@fela.ch>
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
next prev parent reply other threads:[~2004-03-23 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 17:30 Lukas Heiniger
2004-03-19 18:31 ` Daniel Jacobowitz
2004-03-22 13:21 ` Lukas Heiniger
2004-03-22 17:33 ` Daniel Jacobowitz
2004-03-23 19:25 ` Lukas Heiniger
2004-03-23 20:41 ` Daniel Jacobowitz [this message]
2004-03-24 14:44 ` Lukas Heiniger
2004-03-24 14:54 ` Daniel Jacobowitz
2004-03-24 15:09 ` Lukas Heiniger
2004-03-24 15:44 ` Daniel Jacobowitz
2004-03-25 14:29 ` Lukas Heiniger
2004-03-25 15:37 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040323191337.GA28050@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=lukas.heiniger@fela.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox