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: "Yan, Michael" <myan at microstrategy dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 5 Oct 2007 20: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: "Yan, Michael" <myan at microstrategy dot com>
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_64whenpthread_mutex_lock is the innermost function call. bitmode/kernelversion/compiler version are irrelevant
Date: Fri, 5 Oct 2007 16:34:40 -0400
I tried RedHat AS 5 distribution which has glibc version 2.5. It works =
fine.
However, we have to support customers with glibc 2.3 which means we have =
to patch that version. Do you know which change make the difference ? =
Any information is appreciated.
thanks,
Michael
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Friday, October 05, 2007 12:35 PM
To: Yan, Michael
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/2325: wrong back trace on
x86_64whenpthread_mutex_lock is the innermost function call.
bitmode/kernelversion/compiler version are irrelevant
On Fri, Oct 05, 2007 at 12:24:38PM -0400, Yan, Michael wrote:
> Hi Daniel,
>=20
> 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.
--=20
Daniel Jacobowitz
CodeSourcery