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_64whenpthread_mutex_lock is the innermost function call. bitmode/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:38:01 -0000
- Subject: Re: backtrace/2325: wrong back trace on x86_64whenpthread_mutex_lock is the innermost function call. bitmode/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: "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