From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Frank Schaefer <frank.schafer@setuza.cz>, gdb@sources.redhat.com
Subject: Re: Problems debugging forked processes
Date: Sat, 20 Apr 2002 22:21:00 -0000 [thread overview]
Message-ID: <20020421012202.A17852@nevyn.them.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020421091101.2767B-100000@is>
On Sun, Apr 21, 2002 at 09:12:33AM +0300, Eli Zaretskii wrote:
>
> On Fri, 19 Apr 2002, Daniel Jacobowitz wrote:
>
> > > (gdb) show follow-fork-mode
> > > Debugger response to a program call of fork or vfork is "parent".
> > > (gdb) set follow-fork-mode child
> > > (gdb) show follow-fork-mode
> > > Debugger response to a program call of fork or vfork is "child".
> >
> > This variable doesn't actually affect GNU/Linux. Yeah, I know, I know.
> > We need a documentation patch to address this; please file a PR
> > (http://sources.redhat.com/gdb/, Bugs).
>
> If someone tells me what should be documented, I'll do that. Now is the
> time, since v5.2 is in pretest.
>
> Is the issue that follow-fork-mode is only supported on a small number of
> systems? If so, what are those systems, and is it enough to have their
> list in the manual?
I believe the only platform to implement this is actually HP/UX:
drow@nevyn:/opt/src/gdb/src/gdb% grep -r CHILD_HAS_FORKED .
./inftarg.c:#if !defined(CHILD_HAS_FORKED)
./config/pa/nm-hppah.h:#define CHILD_HAS_FORKED
./infttrace.c:#if defined(CHILD_HAS_FORKED)
./ChangeLog-1998: (child_has_forked): Now enclosed by a CHILD_HAS_FORKED ifdef
There's a nice new debugging interface in the works for GNU/Linux that
will let us support this some day. But for now, HP/UX only.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-21 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 0:45 Frank Schaefer
2002-04-19 9:10 ` Daniel Jacobowitz
2002-04-20 22:14 ` Eli Zaretskii
2002-04-20 22:18 ` Andrew Cagney
2002-04-20 22:21 ` Daniel Jacobowitz [this message]
2002-04-21 22:47 ` Frank Schaefer
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=20020421012202.A17852@nevyn.them.org \
--to=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=frank.schafer@setuza.cz \
--cc=gdb@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