*** empty log message ***

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

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 901b0d29a0447c05b26e6624ff66353a6ca40e43..af0d1d56d9d7861117057ee4ba6fe38f5d7c3761 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -1,9 +1,29 @@
 
-                       Known problems in GDB 6.1
+                       Known problems in GDB 6.3
 
                See also: http://www.gnu.org/software/gdb/bugs/
 
 
+*** Build problems
+
+build/1411: build fails on hpux 10.20 and hpux 11.00 with CMA threads
+
+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/hpux-thread.c:222: variable-size type declared outside of any function
+
+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.
@@ -68,29 +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.
 
-*** 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.
+*** Threads
 
-arm-*-*
+threads/1650: manythreads.exp
 
-GDB's ARM target, in 6.0, has not been updated to use the new frame
-mechanism.
+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.
 
-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 problem does not occur on newer systems that use the NPTL
+library, and did not occur with GDB 6.1.