aboutsummaryrefslogtreecommitdiff
path: root/gdb/PROBLEMS
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
commitcd87e7699031fb3d82ac056020b1bf7c8f0aab1f (patch)
tree2298c02368df0dbbe060fdccae75527c1ba89498 /gdb/PROBLEMS
parentbc712bbf17bd3c4ead9c0cacc917cd58f7cc5267 (diff)
downloadgdb-cd87e7699031fb3d82ac056020b1bf7c8f0aab1f.zip
gdb-cd87e7699031fb3d82ac056020b1bf7c8f0aab1f.tar.gz
gdb-cd87e7699031fb3d82ac056020b1bf7c8f0aab1f.tar.bz2
* PROBLEMS: Clarify problems with FreeBSD's compiler and suggest
workaround.
Diffstat (limited to 'gdb/PROBLEMS')
-rw-r--r--gdb/PROBLEMS7
1 files changed, 5 insertions, 2 deletions
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 9ffea60..4c460d6 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