mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@science.uva.nl>
To: linux-kernel@vger.kernel.org
Cc: wichert@cistron.nl, ebrunet@quatramaran.ens.fr, torvalds@transmeta.com
Subject: Re: Children first in fork
Date: Fri, 20 Apr 2001 16:56:50 +0200 (MET DST)	[thread overview]
Message-ID: <200104201456.f3KEuor01481@debye.wins.uva.nl> (raw)

The behaviour of CLONE_PTRACE in Linux 2.4.x is different from the
behaviour in 2.2.x.  Linus is describing the 2.4.x. behaviour, where
the program that's doing the tracing will get the events instead of
the "real" parent.  I believe the 2.2.x behaviour was pretty much
useless, and IIRC that was the reason that Linus accepted a patch for
the new behaviour.  I've tested CLONE_PTRACE in the sense that the
development version of GDB contains some code that allows debugging of
any clone() based thread stuff if the threads implementationion
specifies CLONE_PTRACE in its clone() calls.  That way GDB notices new
threads automagically.  It only works on Linux 2.4.x of course, and I
still have to hack something up to make this functionality in GDB
available to the user.

Mark

             reply	other threads:[~2001-04-20 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 14:56 Mark Kettenis [this message]
2001-04-20 17:49 ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 11:35 Éric Brunet
2001-04-19 12:07 ` David Schwartz
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

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=200104201456.f3KEuor01481@debye.wins.uva.nl \
    --to=kettenis@science.uva.nl \
    --cc=ebrunet@quatramaran.ens.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=wichert@cistron.nl \
    /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®