This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
- From: Mark Kettenis <kettenis at chello dot nl>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 10 Jan 2004 20:28:01 -0000
- Subject: Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
- Reply-to: Mark Kettenis <kettenis at chello dot nl>
The following reply was made to PR backtrace/1505; it has been noted by GNATS.
From: Mark Kettenis <kettenis@chello.nl>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
Date: Sat, 10 Jan 2004 21:20:27 +0100 (CET)
This is pretty weird given the fact that the clone() syscall stub in
glibc explicitly clears %ebp to mark the outermost frame. I'll see if
I can reproduce this.
Mark