2004-03-19  Andrew Cagney  <cagney@redhat.com>
 
 	* PROBLEMS: Add general section titles, remove references to
 	specific releases.
 
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.24
diff -c -r1.24 PROBLEMS
*** PROBLEMS	17 Mar 2004 07:00:41 -0000	1.24
--- PROBLEMS	19 Mar 2004 16:09:11 -0000
***************
*** 3,29 ****
  
  		See also: http://www.gnu.org/software/gdb/bugs/
  
- mips*-*-*
- powerpc*-*-*
- sparc*-*-*
  
! GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
! to use the new frame mechanism.
  
! 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.
! 
! arm-*-*
! 
! GDB's ARM target, in 6.0, has not been updated to use the new frame
! mechanism.
  
! 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).
  
! *** Regressions since gdb 6.0
  
  gdb/826: variables in C++ namespaces have to be enclosed in quotes
  
--- 3,19 ----
  
  		See also: http://www.gnu.org/software/gdb/bugs/
  
  
! *** Misc
  
! gdb/1560: Control-C does not always interrupt GDB.
  
! When GDB is busy processing a command which takes a long time to
! complete, hitting Control-C does not have the expected effect.
! The command execution is not aborted, and the "QUIT" message confirming
! the abortion is displayed only after the command has been completed.
  
! *** C++ support
  
  gdb/826: variables in C++ namespaces have to be enclosed in quotes
  
***************
*** 36,46 ****
  typed in a certain way (e.g. "const char*" as opposed to "const char *"
  or "char const *" or "char const*").
  
- 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.
- 
  gdb/1512: no canonical way to output names of C++ types
  
  We currently don't have any canonical way to output names of C++ types.
--- 26,31 ----
***************
*** 59,73 ****
  function, not to variables defined with types that are defined somewhere
  outside any function (which most types are).
  
- gdb/1560: Control-C does not always interrupt GDB.
- 
- When GDB is busy processing a command which takes a long time to
- complete, hitting Control-C does not have the expected effect.
- The command execution is not aborted, and the "QUIT" message confirming
- the abortion is displayed only after the command has been completed.
- 
- *** Regressions since gdb 5.3
- 
  gdb/1091: Constructor breakpoints ignored
  gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
  
--- 44,49 ----
***************
*** 85,87 ****
--- 61,89 ----
  function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
  ABI for C++ which requires multiple object code functions.
  
+ *** Stack backtraces
+ 
+ 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.
+ 
+ mips*-*-*
+ powerpc*-*-*
+ sparc*-*-*
+ 
+ GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
+ to use the new frame mechanism.
+ 
+ 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.
+ 
+ arm-*-*
+ 
+ GDB's ARM target, in 6.0, has not been updated to use the new frame
+ mechanism.
+ 
+ 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).