This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 2 Aug 2003 01:38:00 -0000
- Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
- Reply-to: Michael Elizabeth Chastain <mec at shout dot net>
The following reply was made to PR symtab/1253; it has been noted by GNATS.
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
Date: Fri, 1 Aug 2003 21:36:54 -0400
Ah, you are right, this is likely to be caused by the 'sleep'
on the stack rather than the hand function call.
My glibc is 2.2.93-5-rh.
I see the same problem in Elena Z's test runs on red hat linux 9
with glibc 2.3.2-27.9-rh. I expect that it has something to do with
the stripped vendor glibc.
I tried static-linking the executables and the backtraces work
with the static-linked executables, both dwarf-2 and stabs+.
That's weird.
Michael C