This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
- From: chastain at sourceware dot org
- To: gdb-prs at sources dot redhat dot com, mec dot gnu at mindspring dot com, nobody at sources dot redhat dot com
- Date: 6 Aug 2004 14:13:21 -0000
- Subject: Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
- Reply-to: chastain at sourceware dot org, gdb-prs at sources dot redhat dot com, mec dot gnu at mindspring dot com, nobody at sources dot redhat dot com, gdb-gnats at sources dot redhat dot com
Synopsis: [regression] gdb prints a bad backtrace for a thread
State-Changed-From-To: open->closed
State-Changed-By: chastain
State-Changed-When: Fri Aug 6 14:13:21 2004
State-Changed-Why:
This bug has been fixed in gdb HEAD 2004-08-01.
Stack backtraces in threads terminate properly now, on my test system at least (native i686-pc-linux-gnu, red hat 8, glibc 2.2.93-5-rh).
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1505