From: "Glenn F. Maynard" <g_gdb@zewt.org>
To: gdb@sourceware.cygnus.com
Subject: gdb: detection and/or fork+gethostbyname crash workaround?
Date: Mon, 23 Jul 2001 18:01:00 -0000 [thread overview]
Message-ID: <20010723210115.B1359@zewt.org> (raw)
Is there any way to tell if a (C) program is being debugged by gdb?
I've had the "dynamic linking in a forked process being debugged"
bite me twice now. The first time around, I moved the process
to another binary (a resolver binary; exec()ing it fixed this). I'm
trying to work around this bug in another program, now, where making
a separate binary for resolving is undesirable; I want to force it
to not fork resolves when being debugged, and do so automatically.
Portability isn't much of a concern: the workaround can be autoconf'd
to only happen on the architectures it works (and/or is necessary) for.
Alternatively, a workaround for this particular bug would be equally
sufficient. Of course, having it fixed would be nice ... it's been around
for at least a year and prevents all "fork for DNS" code from working under
gdb unless it happens to exec to do so, and it's an odd enough bug
that it's probably cost a great deal of time for those hit by it. (It's
been reported multiple times in both the "forked gethostbyname crashes"
and "forked dynamic linking crashes" guises.)
--
Glenn Maynard
next reply other threads:[~2001-07-23 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 18:01 Glenn F. Maynard [this message]
2001-07-24 9:23 ` Kevin Buettner
2001-07-24 11:22 ` Glenn F. Maynard
2001-07-24 13:26 ` Daniel Jacobowitz
2001-07-24 13:44 ` Kevin Buettner
2001-07-24 13:26 ` Kevin Buettner
2001-07-24 13:57 ` Glenn F. Maynard
2001-07-24 14:49 ` Kevin Buettner
2001-07-24 14:22 ` Daniel Jacobowitz
2001-07-24 13:54 ` Mark Kettenis
2001-07-24 13:00 Michael Elizabeth Chastain
2001-07-24 13:53 ` Kevin Buettner
2001-07-24 14:26 ` Glenn F. Maynard
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=20010723210115.B1359@zewt.org \
--to=g_gdb@zewt.org \
--cc=gdb@sourceware.cygnus.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