From cd87e7699031fb3d82ac056020b1bf7c8f0aab1f Mon Sep 17 00:00:00 2001 From: Mark Kettenis Date: Sat, 24 Aug 2002 14:36:12 +0000 Subject: [PATCH] * PROBLEMS: Clarify problems with FreeBSD's compiler and suggest workaround. --- gdb/ChangeLog | 3 +++ gdb/PROBLEMS | 7 +++++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 25a0285..7058e62 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,8 @@ 2002-08-24 Mark Kettenis + * 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 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 -- 2.7.4