X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=gdb%2FPROBLEMS;h=af0d1d56d9d7861117057ee4ba6fe38f5d7c3761;hb=ff800d76d32087301f7aea21e6a030190f940809;hp=7baf1d2e831d8be253c643f3b919d6a377821836;hpb=860660cb5bba4aeb570c609c5d3a3288468f2adf;p=deliverable%2Fbinutils-gdb.git

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 7baf1d2e83..af0d1d56d9 100644
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -1,34 +1,28 @@
 
-			Known problems in GDB 6.2
+			Known problems in GDB 6.3
 
 		See also: http://www.gnu.org/software/gdb/bugs/
 
 
 *** Build problems
 
-build/1458: compile failed on hpux11
+build/1411: build fails on hpux 10.20 and hpux 11.00 with CMA threads
 
-GDB has build problems on HP/UX 11 with some versions of the HP
-Ansi C compiler.  (GCC works fine).
+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:
 
-The problem happens when compiling intl/bindtextdom.c.
-The error is:
+  ../../gdb/hpux-thread.c:222: variable-size type declared outside of any function
 
-  cc: "gettextP.h", line 50: error 1000: Unexpected symbol: "SWAP".
-  cc: panic 2017: Cannot recover from earlier errors, terminating.
-  *** Error exit code 1
+This happens only if the CMA thread package is installed.
 
-This is a problem with the 'inline' keyword in gettextP.h.
-The workaround is to disable 'inline' before building gdb:
+As a workaround, you can disable support for CMA threads
+by editing the file gdb/configure.  Find the line:
 
-  export ac_cv_c_inline=no
+  if test -f /usr/include/dce/cma_config.h ; then
 
-This problem happens only with some versions of the HP Ansi C compiler.
-Versions A.11.01.25171.GP and B.11.11.28706.GP have both been observed
-to work; version B.11.11.04 gets the build error and needs the
-workaround.
+And replace it with:
 
-This problem might also happen with other C compilers.
+  if false ; then
 
 *** Misc
 
@@ -94,38 +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
+*** Threads
 
-GDB's core code base has been updated to use a new backtrace
-mechanism.  This mechanism makes it possible to support new features
-such DWARF 2 Call Frame Information (which in turn makes possible
-backtraces through optimized code).
+threads/1650: manythreads.exp
 
-Since this code is new, it is known to still have a few problems:
+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.
 
-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/).
+This problem does not occur on newer systems that use the NPTL
+library, and did not occur with GDB 6.1.