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 02:18:01 -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: ezannoni@comcast.net, gdb-gnats@sources.redhat.com,
gdb-prs@sources.redhat.com, nobody@sources.redhat.com
Cc:
Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
Date: Fri, 1 Aug 2003 22:10:07 -0400
I don't think it's vsyscall because:
. It happens on red hat linux 8 which is earlier than vsyscall (I think).
. It goes away when I use gdb 5.3 instead of gdb HEAD, on the same
executable.
. It goes away when I link my executable with -static.
I will roll up my sleeves and dive in. I probably can't come with
a coherent fix but maybe I can produce an executable that exhibits
the problem and does not depend on my shared libc.
Michael C