* serial.h (SERIAL_SET_TTY_STATE): Comment return value.

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

diff --git a/gdb/README b/gdb/README
index c8e0206203e668afefcba0a3287a48ca01c29052..d4834e247862cb063e4d4311242c4948cdcfac41 100644 (file)
--- a/gdb/README
+++ b/gdb/README
@@ -452,9 +452,9 @@ Known bugs:
   * Under Ultrix 4.2 (DECstation-3100) or Alphas under OSF/1, we have
     seen problems with backtraces after interrupting the inferior out
     of a read().  The problem is caused by ptrace() returning an
-    incorrect value for the frame pointer register (15 or 30).  As far
-    as we can tell, this is a kernel problem.  Any help with this
-    would be greatly appreciated.
+    incorrect value for the frame pointer register (register 15 or
+    30).  As far as we can tell, this is a kernel problem.  Any help
+    with this would be greatly appreciated.
 
   * On the SPARC GDB reports incorrect values of struct arguments to
     functions, for the seventh and subsequent arguments.  We have been looking
@@ -464,12 +464,6 @@ Known bugs:
     various BFD modules.  None of them is a cause for alarm, they are actually
     a result of bugs in the DECstation compiler.
 
-  * On Solaris (2.1, at least) using the "run" command when the program
-    is already running restarts the program, but may leave a core dump
-    from the previous execution in the current directory.  Other SVR4
-    based systems don't seem to have this problem, using the same gdb
-    source code.
-
   * Notes for the DEC Alpha using OSF/1:
     The debugging output of native cc has two known problems; we view these
     as compiler bugs.
@@ -478,17 +472,14 @@ Known bugs:
     dbx has the same problems with those executables.  A workaround is to
     specify -Wl,-b when linking, but that will increase the executable size
     considerably.
-    If a structure is declared as opaque in one file (e.g. "struct foo *"
+    If a structure has incomplete type in one file (e.g. "struct foo *"
     without a definition for "struct foo"), gdb will be unable to find the
-    structure definition in another file.
-    It has been reported that the Ultrix 4.3A compiler on destations has the
+    structure definition from another file.
+    It has been reported that the Ultrix 4.3A compiler on decstations has the
     same problems.
 
-    If you intend to compile gdb with gcc-2.4.5, be warned that the file
-    bfd/libbfd.c will be miscompiled due to a bug in gcc, you have
-    to compile this file with native cc.  You will get many warnings from
-    gcc while compiling gdb, but these can be ignored for now.  Again, these
-    problems are Alpha-specific.
+    If you compile gdb with gcc-2.4.5, you will get many warnings,
+    but these can be ignored for now.  Again, this problem is Alpha-specific.
 
 GDB can produce warnings about symbols that it does not understand.  By
 default, these warnings are disabled.  You can enable them by executing