This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[patch/rfc] PROBLEMS: Stack backtraces
- From: Andrew Cagney <cagney at gnu dot org>
- To: gdb-patches at sources dot redhat dot com
- Date: Fri, 26 Mar 2004 12:11:50 -0500
- Subject: [patch/rfc] PROBLEMS: Stack backtraces
Hello,
The attached updates the PROBLEMS: Stack backtraces section so that it
is more current.
comments, it's intended for 6.1
Andrew
2004-03-26 Andrew Cagney <cagney@redhat.com>
* PROBLEMS (Stack backtraces): Rewrite. Remove reference to
arm*-*-*.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.23.2.3
diff -u -r1.23.2.3 PROBLEMS
--- PROBLEMS 25 Mar 2004 21:20:26 -0000 1.23.2.3
+++ PROBLEMS 26 Mar 2004 17:05:53 -0000
@@ -63,27 +63,36 @@
*** Stack backtraces
+GDB's code base is being been updated to use a new backtrace
+mechanism. This mechanism makes possible the support of new features
+such DWARF 2 Call Frame Information (which in turn makes possible
+backtraces through optimized code).
+
+Since this code is new, it is known to still have a few problems:
+
gdb/1505: [regression] gdb prints a bad backtrace for a thread
-When backtracing a thread, gdb doesn't stop until it hits garbage.
-This is sensitive to the operating system and thread library.
+When backtracing a thread, gdb does not stop when it reaches the outer
+most frame, instead continuing until it hits garbage. This is
+sensitive to the operating system and thread library.
+hppa*-*-*
mips*-*-*
-powerpc*-*-*
-sparc*-*-*
-GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
-to use the new frame mechanism.
+The MIPS and HPPA backtrace code has only very recently been updated
+to use GDB's new frame mechanism. At present there are still a few
+problems, in particular backtraces through signal handlers do not
+work.
+
+People encountering problems with these architectures should consult
+GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
+to see if there are updates.
-People encountering problems with these targets should consult GDB's
-web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
-if there is an update.
-
-arm-*-*
+powerpc*-*-*
-GDB's ARM target, in 6.0, has not been updated to use the new frame
-mechanism.
+PowerPC architecture support, in 6.1, does not use the new frame code.
-Fortunately the ARM target, in the GDB's mainline sources, has been
-updated so people encountering problems should consider downloading a
-more current GDB (http://www.gnu.org/software/gdb/current).
+Fortunately the PowerPC architecture support, in the GDB's mainline
+sources, has been updated. People encountering problems should
+consider downloading a more current GDB
+(http://www.gnu.org/software/gdb/current/).