This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: symtab/619: lockup during backtrace or program crash
- From: mec at shout dot net
- To: elanthis at awesomeplay dot com, gdb-prs at sources dot redhat dot com, mec at shout dot net, nobody at sources dot redhat dot com
- Date: 19 Aug 2003 06:32:22 -0000
- Subject: Re: symtab/619: lockup during backtrace or program crash
- Reply-to: mec at shout dot net, elanthis at awesomeplay dot com, gdb-prs at sources dot redhat dot com, mec at shout dot net, nobody at sources dot redhat dot com, gdb-gnats at sources dot redhat dot com
Synopsis: lockup during backtrace or program crash
Responsible-Changed-From-To: unassigned->chastain
Responsible-Changed-By: chastain
Responsible-Changed-When: Tue Aug 19 06:32:22 2003
Responsible-Changed-Why:
I'm running through the old gdb bugs. This bug is 13 months old!
State-Changed-From-To: open->feedback
State-Changed-By: chastain
State-Changed-When: Tue Aug 19 06:32:22 2003
State-Changed-Why:
Beautiful, this is just what we need: an executable file and a core file.
gdb 5.2.1 does lock up. But gdb 5.3 works fine, giving me a good looking backtrace. A prerelease version of gdb 6.0 works fine, too.
Can you try again with gdb 5.3 or later, and give me a little feedback on whether it works for you?
Michael C
GDB QA Guy
(Formerly, Furey of Merc Industries)
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=619