* remote-fileio.c (remote_fileio_return_success): Take a gdb_byte

[deliverable/binutils-gdb.git] / gdb / PROBLEMS

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 9a0127dfd61cb5c35753461db30e606999d1ecb9..af0d1d56d9d7861117057ee4ba6fe38f5d7c3761 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -1,27 +1,51 @@
 
-                       Known problems in GDB 6.0
+                       Known problems in GDB 6.3
 
                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.
+*** Build problems
 
-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.
+build/1411: build fails on hpux 10.20 and hpux 11.00 with CMA threads
 
-arm-*-*
+GDB does not build on HP/UX 10.20 or HP/UX 11.00 if the CMA
+thread package is installed.  The compile error is:
 
-GDB's ARM target, in 6.0, has not been updated to use the new frame
-mechanism.
+  ../../gdb/hpux-thread.c:222: variable-size type declared outside of any function
 
-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).
+This happens only if the CMA thread package is installed.
+
+As a workaround, you can disable support for CMA threads
+by editing the file gdb/configure.  Find the line:
+
+  if test -f /usr/include/dce/cma_config.h ; then
+
+And replace it with:
+
+  if false ; then
+
+*** 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/931: GDB could be more generous when reading types C++ templates on input
+
+When the user types a template, GDB frequently requires the type to be
+typed in a certain way (e.g. "const char*" as opposed to "const char *"
+or "char const *" or "char const*").
+
+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.
+E.g. "const char *" versus "char const *"; more subtleties arise when
+dealing with templates.
 
 gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
 
@@ -35,6 +59,18 @@ This applies only to classes where the class type is defined inside a
 function, not to variables defined with types that are defined somewhere
 outside any function (which most types are).
 
+gdb/1588: names of c++ nested types in casts must be enclosed in quotes
+
+You must type
+  (gdb) print ('Foo::Bar') x
+or
+  (gdb) print ('Foo::Bar' *) y
+instead of
+  (gdb) print (Foo::Bar) x
+or
+  (gdb) print (Foo::Bar *) y
+respectively.
+
 gdb/1091: Constructor breakpoints ignored
 gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
 
@@ -52,8 +88,13 @@ implement virtual base classes.  gcc 2.x generated just one object code
 function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
 ABI for C++ which requires multiple object code functions.
 
-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.
+*** Threads
+
+threads/1650: manythreads.exp
+
+On GNU/Linux systems that use the old LinuxThreads thread library, a
+program rapidly creating and deleting threads can confuse GDB leading
+to an internal error.
+
+This problem does not occur on newer systems that use the NPTL
+library, and did not occur with GDB 6.1.