diff options
| author | Andrew Cagney <cagney@redhat.com> | 2004-07-26 18:30:19 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2004-07-26 18:30:19 +0000 |
| commit | a1b461bf403f675bf552b7f6783a732aa34056d7 (patch) | |
| tree | ca90fc2677e0e8180845a0c12f002f24eed29232 /gdb/PROBLEMS | |
| parent | cb1a6d5f515a44ffcdc3bbf20c2e01ee8a37670d (diff) | |
| download | gdb-a1b461bf403f675bf552b7f6783a732aa34056d7.zip gdb-a1b461bf403f675bf552b7f6783a732aa34056d7.tar.gz gdb-a1b461bf403f675bf552b7f6783a732aa34056d7.tar.bz2 | |
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/PROBLEMS | 21 |
1 files changed, 0 insertions, 21 deletions
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/). |