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: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 19 Jul 2004 21:08:00 -0000
- Subject: Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
- Reply-to: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
The following reply was made to PR backtrace/1505; it has been noted by GNATS.
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org
Cc: gdb-gnats@sources.redhat.com
Subject: Re: backtrace/1505: [regression] gdb prints a bad backtrace for a thread
Date: Mon, 19 Jul 2004 17:06:26 -0400 (EDT)
Eli Zaretskii writes:
eliz> FWIW, I've seen similar problems without any threading, in the DJGPP
eliz> port (when debugging Emacs). GDB 5.x doesn't have problems with the
eliz> same debuggee. I originally thought that it is specific to DJGPP
eliz> (perhaps because the DJGPP port of Emacs is compiled with -gcoff and
eliz> the line number table overflows the 64K limit inherent to COFF debug
eliz> info), but now that I see this PR, I begin to think that it's not
eliz> DJGPP-specific.
Can you grab a gdb session (somehow) and cut the part where you actually
type 'backtrace' and add that to pr 1505?
Just replying to this mail ought to do that (mail to gdb-gnats@,
with subject 'Re: backtrace/1505: ...).
Michael C