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: 11 Jan 2004 14:18:00 -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: Sun, 11 Jan 2004 15:10:48 +0100 (CET)
I can't reproduce this on any (SuSE 7.2, RedHat 9) system :-(. It
occurs to me that it is pretty weird that frame #3 has a zero PC at
all. I'd expect that the PC for this frame would be somewhere in
clone(), which is indeed what I see on RedHat 9.
It'd be interesting to see the output from "info frame" for frames #2
and #3. I'm also curious about the value of $eip, $esp and $ebp in
those frames.
I really suspect that this is a problem with libc.so or libpthread.so
on your system.
Mark