summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Kettenis <kettenis@gnu.org>2002-08-24 14:36:12 +0000
committerMark Kettenis <kettenis@gnu.org>2002-08-24 14:36:12 +0000
commitab26b6a4321df940fbe4b26dc483fc007e07dbdd (patch)
tree1bceb31ba95ba40ca54ff57dd211db20ffade87b
parentd4a002ad24400718cc392f15609d32d676cfc340 (diff)
downloadgdb-ab26b6a4321df940fbe4b26dc483fc007e07dbdd.tar.gz
* PROBLEMS: Clarify problems with FreeBSD's compiler and suggest
workaround.
-rw-r--r--gdb/ChangeLog3
-rw-r--r--gdb/PROBLEMS7
2 files changed, 8 insertions, 2 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 25a0285b7de..7058e621300 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,8 @@
2002-08-24 Mark Kettenis <kettenis@gnu.org>
+ * PROBLEMS: Clarify problems with FreeBSD's compiler and suggest
+ workaround.
+
* valprint.c (print_longest) [CC_HAS_LONG_LONG &&
PRINTF_HAS_LONG_LONG]: Cast val_long to (long long) or (unsigned
long long) to prevent compiler warning on 64-bit systems.
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 9ffea60be61..4c460d6eb80 100644
--- 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