From: Andrew Cagney <cagney@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk <frysk@sources.redhat.com>, Tom Tromey <tromey@redhat.com>
Subject: Re: follow-on{fork|clone}
Date: Mon, 03 Mar 2008 14:58:00 -0000 [thread overview]
Message-ID: <47CC1212.4050000@redhat.com> (raw)
In-Reply-To: <47CC0BF7.2090604@redhat.com>
Phil,
Consider:
(fhpd) load gcc
(fhpd) break cc1.c#foo
(fhpd) run test.c -o test
which involves forks, and possibly execs. From the user's point-of-view
that should "just work". This means automatically (no interaction)
following forks and execs. This has always been our goal.
An option to disable the automatic behavior may be interesting, but can
be added later.
Andrew
next prev parent reply other threads:[~2008-03-03 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:32 follow-on{fork|clone} Phil Muldoon
2008-03-03 14:58 ` Andrew Cagney [this message]
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=47CC1212.4050000@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=pmuldoon@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).