2004-03-28 Andrew Cagney <cagney@redhat.com>

	* PROBLEMS (Stack backtraces): Rewrite.  Remove reference to
	arm*-*-*.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index c5812d430867eea03ba5c1cf9b8c114a790196d6..1a859415cc84904c2d9b9a801269ea0e970c6ef3 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2004-03-28  Andrew Cagney  <cagney@redhat.com>
+
+       * PROBLEMS (Stack backtraces): Rewrite.  Remove reference to
+       arm*-*-*.
+
 2004-03-28  Stephane Carrez  <stcarrez@nerim.fr>
 
        * tui/tui-regs.c (tui_show_registers): Make sure the TUI is active

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 901b0d29a0447c05b26e6624ff66353a6ca40e43..0a5a1cd3df6bdcaebd55429f790a9264b7cbd662 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -70,27 +70,36 @@ ABI for C++ which requires multiple object code functions.
 
 *** Stack backtraces
 
+GDB's core code base has been updated to use a new backtrace
+mechanism.  This mechanism makes it possible to support 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
+outermost 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 targets should consult GDB's
-web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
-if there is an update.
+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.
 
-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, PowerPC architecture support, in GDB's mainline sources,
+have been updated.  People encountering problems should consider
+downloading a more current snapshot of GDB
+(http://www.gnu.org/software/gdb/current/).