From: Phil Muldoon <pmuldoon@redhat.com>
To: frysk <frysk@sources.redhat.com>, Tom Tromey <tromey@redhat.com>
Subject: follow-on{fork|clone}
Date: Mon, 03 Mar 2008 14:32:00 -0000 [thread overview]
Message-ID: <47CC0BF7.2090604@redhat.com> (raw)
Tom
This is something you have brought up before on at various times, and
lists, and I thought once and for all to collate some knowledge here.
Given that you turn off follow-on-fork sometimes (in GDB) is that
mechanic useful for Frysk as well? Why do you turn it off? Is it because
of bugs, or more of a focus?
I ask mainly to collate user experience here and see if it's a valid
feature. In writing watchpoints I personally cannot see why
follow-on-{fork|clone} would ever be turned off, but it occurs to me
then that the mechanic might be desirable elsewhere.
What do you think?
Regards
Phil
next reply other threads:[~2008-03-03 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:32 Phil Muldoon [this message]
2008-03-03 14:58 ` follow-on{fork|clone} Andrew Cagney
2008-03-03 16:27 ` follow-on{fork|clone} Tom Tromey
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=47CC0BF7.2090604@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).