public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Horsley <Tom.Horsley@mail.ccur.com>
To: linux-kernel@vger.kernel.org
Subject: Is this a clone() failing?
Date: Mon, 22 Oct 2001 15:13:40 GMT	[thread overview]
Message-ID: <200110221513.PAA24852@amber2.ccur.com> (raw)

Consider the case of a debugger which also happens to be a multi-threaded
application. From what I understand, clone() is supposed to allow you to
inherit all attributes so the different threads can act like they are really
part of the same program, but it turns out that the thread which does the
ptrace "attach" is the only thread the kernel thinks should be allowed to do
any other operations on the process being debugged.

Should there be a new "clone debug privileges" flag?

Or is this just something (multi-threaded) debuggers have to live with?

(It wasn't too hard to force a single thread to always be the one that does
all ptrace() calls).
--
Tom.Horsley@mail.ccur.com                \\\\      Will no one rid me of
Concurrent Computers, Ft. Lauderdale, FL    \\\\     this troublesome
Me: http://home.att.net/~Tom.Horsley/          \\\\     autoconf?
Project Vote Smart: http://www.vote-smart.org     \\\\    !!!!!

                 reply	other threads:[~2001-10-22 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200110221513.PAA24852@amber2.ccur.com \
    --to=tom.horsley@mail.ccur.com \
    --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