public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Pavel Kankovsky <peak@argo.troja.mff.cuni.cz>,
	Mike Coleman <mkc@mathdogs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PTRACE_ATTACH breaks wait4()
Date: Fri, 08 Jun 2001 09:47:20 +0100	[thread overview]
Message-ID: <28783.991990040@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from Pavel Kankovsky <peak@argo.troja.mff.cuni.cz>  of "Thu, 07 Jun 2001 22:39:43 +0200." <20010607223921.D94.0@argo.troja.mff.cuni.cz>

I have an idea for getting around this problem, but it's only half implemented
at the moment (I use it for implementing a Wine server in the kernel). It
involves having a list things called task ornaments attached to each
process. Each ornament has a table of event notification methods (so it can be
informed about fork, execve, signal and exit events). Signal event
notification methods are able to prevent a signal from propegating further
down the chain, and the parent's wait handler would be the last element in
this list. When a process attaches with ptrace(), it would insert another
ornament into this list, before the parent's ornament. This means (a) the
process doesn't have to be reparented, and (b) more than one debugger can
actually attach to a process (eg: strace and gdb both).

This would, however, mean that wait*() would have to not only look at a
process's list of children, but also it's list of processes it has ornamented
via ptrace

David

      parent reply	other threads:[~2001-06-08  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 20:39 PTRACE_ATTACH breaks wait4() Pavel Kankovsky
2001-06-08  6:19 ` Mike Coleman
2001-06-08  8:47 ` David Howells [this message]

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=28783.991990040@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkc@mathdogs.com \
    --cc=peak@argo.troja.mff.cuni.cz \
    /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