From a1b461bf403f675bf552b7f6783a732aa34056d7 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Mon, 26 Jul 2004 18:30:19 +0000 Subject: 2004-07-26 Andrew Cagney * 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. --- gdb/PROBLEMS | 21 --------------------- 1 file changed, 21 deletions(-) (limited to 'gdb/PROBLEMS') diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index 2bb66bb..1fa3538 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/). -- cgit v1.1