RE: backtrace/2325: wrong back trace on x86_64 whenpthread_mutex_lock is the innermost function call. bit mode/kernelversion/compiler version are irrelevant

RE: backtrace/2325: wrong back trace on x86_64 whenpthread_mutex_lock is the innermost function call. bit mode/kernelversion/compiler version are irrelevant

[Yan, Michael]

The following reply was made to PR backtrace/2325; it has been noted by GNATS.

From: "Yan, Michael" <myan@microstrategy.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb-gnats@sources.redhat.com>
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
Date: Fri, 5 Oct 2007 12:24:38 -0400

 Hi Daniel,
 
 We are using glibc 2.3.2 and 2.3.4. Our customers use it too. Is there a =
 way to work around this on gdb side ?
 
 
 $ /lib64/tls/libc.so.6
 GNU C Library stable release version 2.3.4, by Roland McGrath et al.
 Copyright (C) 2005 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.
 There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
 PARTICULAR PURPOSE.
 Compiled by GNU CC version 3.4.6 20060404 (Red Hat 3.4.6-3).
 Compiled on a Linux 2.4.20 system on 2007-01-31.
 Available extensions:
         GNU libio by Per Bothner
         crypt add-on version 2.1 by Michael Glad and others
         Native POSIX Threads Library by Ulrich Drepper et al
         RT using linux kernel aio
         The C stubs add-on version 2.1.2.
         GNU Libidn by Simon Josefsson
         BIND-8.2.3-T5B
         NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
 Thread-local storage support included.
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/libc/bugs.html>.
 
 thanks,
 Michael
 
 -----Original Message-----
 From: Daniel Jacobowitz [mailto:drow@false.org]
 Sent: Friday, October 05, 2007 12:02 PM
 To: Yan, Michael
 Cc: gdb-gnats@sources.redhat.com
 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
 
 
 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.
 
 --=20
 Daniel Jacobowitz
 CodeSourcery

Re: backtrace/2325: wrong back trace on x86_64 whenpthread_mutex_lock is the innermost function call. bit mode/kernelversion/compiler version are irrelevant

[Daniel Jacobowitz]

The following reply was made to PR backtrace/2325; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@false.org>
To: "Yan, Michael" <myan@microstrategy.com>
Cc: gdb-gnats@sources.redhat.com
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
Date: Fri, 5 Oct 2007 12:34:47 -0400

 On Fri, Oct 05, 2007 at 12:24:38PM -0400, Yan, Michael wrote:
 > Hi Daniel,
 > 
 > We are using glibc 2.3.2 and 2.3.4. Our customers use it too. Is
 > there a way to work around this on gdb side ?
 
 Not that I know of.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery