From: "David Schwartz" <davids@webmaster.com>
To: "Éric Brunet" <ebrunet@quatramaran.ens.fr>, linux-kernel@vger.kernel.org
Subject: RE: Children first in fork
Date: Thu, 19 Apr 2001 05:07:11 -0700 [thread overview]
Message-ID: <NCBBLIEPOCNJOAEKBEAKAEEJOHAA.davids@webmaster.com> (raw)
In-Reply-To: <20010419133538.A28654@quatramaran.ens.fr>
> Hello all,
>
> I have read on lwn.net that the patch that makes children run first after
> a fork has been integrated in the latest pre-kernel.
>
> I am a little bit concerned by that, as I have begun to write a program
> that monitors process using ptrace. The difficulty is to ptrace-attach
> the child in a fork before it can do anything unmonitored. When the
> parent runs first, the return from the fork system called is trapped by
> the monitor program which has enough time to ptrace-attach the child. If
> the child runs first, it is not even remotely the case anymore.
>
> I understand that performance is more important that the possibility to
> ptrace across forks, but I still think that there should be a way to
> attach the children of a ptraced-process. Is there currently a way to
> achieve this in the kernel that I am not aware of ?
It seems to me that what you really want is a fork option to create the
child in a suspended state.
DS
next prev parent reply other threads:[~2001-04-19 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 11:35 Éric Brunet
2001-04-19 12:07 ` David Schwartz [this message]
2001-04-19 12:56 ` Éric Brunet
2001-04-19 16:31 ` Wichert Akkerman
2001-04-19 17:58 ` Linus Torvalds
2001-04-20 7:46 ` Wichert Akkerman
2001-04-20 10:27 ` Thomas Pornin
2001-04-20 10:13 ` Éric Brunet
2001-04-20 17:47 ` Linus Torvalds
2001-04-20 14:56 Mark Kettenis
2001-04-20 17:49 ` Linus Torvalds
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=NCBBLIEPOCNJOAEKBEAKAEEJOHAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=ebrunet@quatramaran.ens.fr \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®