This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Stack "signal handler called"
- From: Daniel Jacobowitz <drow at false dot org>
- To: Fabian Cenedese <Cenedese at indel dot ch>
- Cc: gdb at sources dot redhat dot com
- Date: Sun, 3 Oct 2004 14:42:30 -0400
- Subject: Re: Stack "signal handler called"
- References: <5.2.0.9.1.20040930114255.01ce7bf0@NT_SERVER>
On Thu, Sep 30, 2004 at 11:45:46AM +0200, Fabian Cenedese wrote:
> Hi
>
> I tried to examine a target where a thread had crashed. I issued bt
> and got only one frame, somewhere in memcpy.c. For the second
> frame gdb only printed <signal handler called>. What does this mean?
> I found the string in stack.c but I couldn't make out the meaning.
> Does it mean that the call stack was destroyed? Some invalid
> addresses in the call stack?
It means that GDB thinks that a signal handler has been invoked, and
that the frames above it are in the signal handler context. If that's
incorrect, you've found a bug in GDB.
(You mentioned threads. It may be that the application is placing
thread stacks in such a way that GDB is confused...)
--
Daniel Jacobowitz