aboutsummaryrefslogtreecommitdiff
path: root/gdb/PROBLEMS
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2004-03-28 19:56:41 +0000
committerAndrew Cagney <cagney@redhat.com>2004-03-28 19:56:41 +0000
commit72b564588119aa210f460cfe94c29d10d7abd1db (patch)
tree08ff8abe74dc465a7a7e1cad3b60455e16507266 /gdb/PROBLEMS
parent6a1b180db492f1874502790867619e2c59b90f0a (diff)
downloadgdb-72b564588119aa210f460cfe94c29d10d7abd1db.zip
gdb-72b564588119aa210f460cfe94c29d10d7abd1db.tar.gz
gdb-72b564588119aa210f460cfe94c29d10d7abd1db.tar.bz2
2004-03-28 Andrew Cagney <cagney@redhat.com>
* PROBLEMS (Stack backtraces): Rewrite. Remove reference to arm*-*-*.
Diffstat (limited to 'gdb/PROBLEMS')
-rw-r--r--gdb/PROBLEMS39
1 files changed, 24 insertions, 15 deletions
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 901b0d2..0a5a1cd 100644
--- 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/).