aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2001-12-07 23:33:19 +0000
committerAndrew Cagney <cagney@redhat.com>2001-12-07 23:33:19 +0000
commit6b325864474bb4a71e548b9f99cb704ad94cbbed (patch)
tree7cf9f43bb6f04760a1f787adcc615f71d470ed9f /gdb
parent23abb74e4bdf8c1c1f32052466952bbeff14bd39 (diff)
downloadgdb-6b325864474bb4a71e548b9f99cb704ad94cbbed.zip
gdb-6b325864474bb4a71e548b9f99cb704ad94cbbed.tar.gz
gdb-6b325864474bb4a71e548b9f99cb704ad94cbbed.tar.bz2
PROBLEMS.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog5
-rw-r--r--gdb/PROBLEMS45
-rw-r--r--gdb/README52
3 files changed, 52 insertions, 50 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 184cda8..112f093 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2001-12-07 Andrew Cagney <ac131313@redhat.com>
+
+ * PROBLEMS: New file.
+ * README: Move known problems to PROBLEMS file.
+
2001-12-07 Daniel Jacobowitz <drow@mvista.com>
* stabsread.c (read_member_functions): Skip member functions which
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
new file mode 100644
index 0000000..79bc2cf
--- /dev/null
+++ b/gdb/PROBLEMS
@@ -0,0 +1,45 @@
+hppa2.0-hp-hpux10.20
+
+Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1
+does not build on HP/UX 10.20 when using the HP supplied compiler.
+
+Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with
+GCC.
+
+
+hppa2.0w-hp-hpux11.00
+
+Due to a problem with ltconfig and long argument lines, GDB 5.1 does
+not configure on HP/UX 11.00.
+
+
+alpha-dec-osf5.1
+
+GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A
+GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work
+much better.
+
+
+alpha-dec-osf4.0e
+
+GDB 5.1 is known to have problems on this platform (encounters an
+internal error in the symbol table reader).
+
+
+sparcv9-sun-solaris2.8
+
+There are known problems with building GDB 5.1 using GCC 3.0.x for the
+64 bit SPARC target (bad code gen). You could try a development
+version of GCC.
+
+
+i586-sco-sysv5uw7.1.1
+
+There are known problems with GDB 5.1's thread support on this
+platform. Non-threaded programs should work.
+
+
+*-*-*
+
+GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is
+one such compiler. This problem should be fixed on the trunk.
diff --git a/gdb/README b/gdb/README
index 3568dfc..dcf0a47 100644
--- a/gdb/README
+++ b/gdb/README
@@ -7,6 +7,8 @@ A summary of new features is in the file `NEWS'.
See the GDB home page at http://www.gnu.org/software/gdb/ for up to
date release information, mailing list links and archives, etc.
+See the file PROBLEMS for late breaking news.
+
Unpacking and Installation -- quick overview
==========================
@@ -427,56 +429,6 @@ other GNU tools recursively; but these are the only options that affect
GDB or its supporting libraries.
-Host/target specific installation notes
-=======================================
-
-hppa2.0-hp-hpux10.20
-
-Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1
-does not build on HP/UX 10.20 when using the HP supplied compiler.
-
-Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with
-GCC.
-
-
-hppa2.0w-hp-hpux11.00
-
-Due to a problem with ltconfig and long argument lines, GDB 5.1 does
-not configure on HP/UX 11.00.
-
-
-alpha-dec-osf5.1
-
-GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A
-GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work
-much better.
-
-
-alpha-dec-osf4.0e
-
-GDB 5.1 is known to have problems on this platform (encounters an
-internal error in the symbol table reader).
-
-
-sparcv9-sun-solaris2.8
-
-There are known problems with building GDB 5.1 using GCC 3.0.x for the
-64 bit SPARC target (bad code gen). You could try a development
-version of GCC.
-
-
-i586-sco-sysv5uw7.1.1
-
-There are known problems with GDB 5.1's thread support on this
-platform. Non-threaded programs should work.
-
-
-*-*-*
-
-GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is
-one such compiler. This problem should be fixed on the trunk.
-
-
Remote debugging
=================