From: Daniel Jacobowitz <dan@debian.org>
To: John Reiser <jreiser@BitWagon.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: observe & control thread state for exit futex ?
Date: Sun, 13 Apr 2003 23:35:48 -0400 [thread overview]
Message-ID: <20030414033548.GA4048@nevyn.them.org> (raw)
In-Reply-To: <3E9A2258.9020507@BitWagon.com>
On Sun, Apr 13, 2003 at 07:52:08PM -0700, John Reiser wrote:
> How can a debugger, newly attached to an arbitrary thread, determine whether
> the thread has a pending exit futex and associated memory location to clear
> [CLONE_CHILD_CLEARTID flag and child_tid_ptr parameter at __clone()]?
>
> If so, then how can the debugger determine the address, change the address,
> cancel the futex, and/or intercept the notification?
It can't. Even clone flags are not accessible.
If you can think of a good reason that a debugger would need any
particular piece of data, exposing it is very straightforward.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-14 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 2:52 observe & control thread state for exit futex ? John Reiser
2003-04-14 3:35 ` Daniel Jacobowitz [this message]
2003-04-15 15:01 ` John Reiser
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=20030414033548.GA4048@nevyn.them.org \
--to=dan@debian.org \
--cc=jreiser@BitWagon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.