This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2311: bad stackframe, corrupt backtrace, stacktrace
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 8 Sep 2007 16:58:01 -0000
- Subject: Re: gdb/2311: bad stackframe, corrupt backtrace, stacktrace
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/2311; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: mnemo@minimum.se
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2311: bad stackframe, corrupt backtrace, stacktrace
Date: Sat, 8 Sep 2007 12:54:04 -0400
On Sat, Sep 08, 2007 at 04:24:24PM -0000, mnemo@minimum.se wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1210053952 (LWP 10014)]
> 0x00000000 in ?? ()
> (gdb) bt
> #0 0x00000000 in ?? ()
> #1 0xbfc2a368 in ?? ()
> #2 0x08048391 in main () at main.c:8
> (gdb)
>
>
>
> Notice that the #1 stackframe isn't being properly printed. The expected behaviour is that #1 is presented as asm_jmp_zero function because that's what it represents.
No, it doesn't. It is impossible to print asm_jmp_zero in this case
because jmp does not leave a return address on the stack.
--
Daniel Jacobowitz
CodeSourcery