Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: eliz@is.elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Mention some problems with using GDB on FreeBSD
Date: Sat, 24 Aug 2002 08:09:00 -0000	[thread overview]
Message-ID: <200208241428.g7OESLLe066004@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <8011-Sat24Aug2002123631+0300-eliz@is.elta.co.il>

   Date: Sat, 24 Aug 2002 12:36:32 +0300
   From: "Eli Zaretskii" <eliz@is.elta.co.il>

   > Date: Sat, 24 Aug 2002 02:35:30 +0200 (CEST)
   > From: Mark Kettenis <kettenis@chello.nl>
   > 
   > This patch makes PROBLEMS mention two problems with using GDB on
   > FreeBSD.

   Would it be possible to give users some idea about the phenomena they
   will see as the result of these problems?  As the text goes now, I
   don't think a user could decide whether some problem they see is due
   to this bug or not.

   Also, it might be a good idea to tell them how to work around the bug
   (I'm guessing "gcc -gdwarf-2" or some such?).

Thanks for the suggestion.  I checked in the attached patch.

Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>
	* PROBLEMS: Clarify problems with FreeBSD's compiler and suggest
	workaround.

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.7
diff -u -p -r1.7 PROBLEMS
--- PROBLEMS 23 Aug 2002 23:05:39 -0000 1.7
+++ PROBLEMS 24 Aug 2002 14:27:44 -0000
@@ -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


  reply	other threads:[~2002-08-24 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23 17:41 Mark Kettenis
2002-08-24  2:44 ` Eli Zaretskii
2002-08-24  8:09   ` Mark Kettenis [this message]
2002-08-24 14:05     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200208241428.g7OESLLe066004@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox