This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: backtrace/2325: wrong back trace on x86_64 whenpthread_mutex_lock is the innermost function call. bit mode/kernelversion/compiler version are irrelevant
- 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: 5 Oct 2007 16:08:01 -0000
- Subject: Re: backtrace/2325: wrong back trace on x86_64 whenpthread_mutex_lock is the innermost function call. bit mode/kernelversion/compiler version are irrelevant
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR backtrace/2325; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: myan@microstrategy.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/2325: wrong back trace on x86_64 when
pthread_mutex_lock is the innermost function call. bit mode/kernel
version/compiler version are irrelevant
Date: Fri, 5 Oct 2007 12:01:50 -0400
On Fri, Oct 05, 2007 at 03:43:15PM -0000, myan@microstrategy.com wrote:
> gdb print out wrong back trace on x86_64 whenever the innermost frame is in pthread_mutex_lock.
The last time I checked this was caused by bogus debugging information
for __lll_mutex_lock_wait in glibc. I think it's fixed in current
snapshots of glibc.
--
Daniel Jacobowitz
CodeSourcery