From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Mention some problems with using GDB on FreeBSD
Date: Fri, 23 Aug 2002 17:41:00 -0000 [thread overview]
Message-ID: <200208240035.g7O0ZU65032156@elgar.kettenis.dyndns.org> (raw)
This patch makes PROBLEMS mention two problems with using GDB on
FreeBSD. I've tried to find a workaround for these problems, but up
until now I've not been successfull. I submitted patches to solve the
problems to the FreeBSD people but they have not been integrated yet.
Committed.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* PROBLEMS: Refer to GDB 5.3 instead of 5.2. Mention FreeBSD
problems.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.6
diff -u -p -r1.6 PROBLEMS
--- PROBLEMS 24 May 2002 02:56:56 -0000 1.6
+++ PROBLEMS 23 Aug 2002 22:59:07 -0000
@@ -1,7 +1,24 @@
- Known problems in GDB 5.2
+ Known problems in GDB 5.3
See also: http://www.gnu.org/software/gdb/bugs/
+
+
+*-*-freebsd*
+---------------
+
+Due to a kernel bug (kern/35175), detaching from an attached process
+will very likely cause the process to be stop or die with a Trace/BPT
+trap.
+
+
+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.
hppa2.0-hp-hpux10.20
next reply other threads:[~2002-08-24 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 17:41 Mark Kettenis [this message]
2002-08-24 2:44 ` Eli Zaretskii
2002-08-24 8:09 ` Mark Kettenis
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=200208240035.g7O0ZU65032156@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--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