* gas/m68hc11/m68hc11.exp: Rename from all.exp; run the new tests.

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

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 9ffea60be61dc890b2ef80cba332cabbcf408eeb..b2f45d8bff2e98f3f9798f2788a8060c395442b1 100644 (file)
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -17,8 +17,11 @@ i386-*-freebsd[34]*
 
 There is a bug (bin/41671) in FreeBSD's gcc that causes it to emit bad
 debug information when using the stabs format (which is the default).
-In earlier versions of GDB the effects were rather limited, but
-starting with GDB 5.3 the influence is much more prominent.
+As a result GDB tends to place breakpoints on functions before the
+function prologue, and information about function parameters and local
+variables is lost.  In earlier versions of GDB the effects were rather
+limited, but starting with GDB 5.3 the influence is much more
+prominent.  As a workaround, compile your code with -gdwarf-2.
 
 
 hppa2.0-hp-hpux10.20
@@ -47,3 +50,18 @@ i386-*-freebsd4.4*
 
 gdb/455: GDB doesn't build on a FreeBSD 4.4-STABLE system.  The
 problem is still being investigated.
+
+alpha*-*-osf*
+-------------
+
+gdb/816: When building GDB with GCC 3.0.1, GDB is unable to load a core
+file properly. It generates several errors and warnings regarding
+unhandled core file section types, incorrect endianness, the failure to
+load the registers. Are also incorrectly reported: The program name, the
+cause of the program death, and the call stack at the moment of the
+death. This problem has been reported on alpha-osf4.0f and alpha-osf5.1a.
+To work-around the problem, add -D__digital__ to the CFLAGS when
+building GDB vis:
+
+    $ make CFLAGS='-O2 -D__digital__'
+