summaryrefslogtreecommitdiff
path: root/gdb/PROBLEMS
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2004-07-26 18:30:19 +0000
committerAndrew Cagney <cagney@redhat.com>2004-07-26 18:30:19 +0000
commit747e40d9d6c9929fcab6e5a3e923d0f5360cf9b4 (patch)
treee57dd282b7a73490a14e8676a0d47d31ca181ee3 /gdb/PROBLEMS
parent1cc270bab1b1c8254b9f41a86d48882ca9fec521 (diff)
downloadgdb-747e40d9d6c9929fcab6e5a3e923d0f5360cf9b4.tar.gz
2004-07-26 Andrew Cagney <cagney@gnu.org>
* MAINTAINERS: Mark the xstormy16, sh64, ns32k, mn10300, mcore, and h8300 as broken. * NEWS: END-OF-LIFE frame compatibility module. * PROBLEMS: For "Stack backtraces", remove powerpc, hppa and mips specific comments.
Diffstat (limited to 'gdb/PROBLEMS')
-rw-r--r--gdb/PROBLEMS21
1 files changed, 0 insertions, 21 deletions
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 2bb66bbd8df..1fa353838c7 100644
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -121,24 +121,3 @@ gdb/1505: [regression] gdb prints a bad backtrace for a thread
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*-*-*
-
-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.
-
-powerpc*-*-*
-
-PowerPC architecture support, in 6.1, does not use the new frame code.
-
-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/).