From: Phil Muldoon <pmuldoon@redhat.com>
To: Frysk Hackers <frysk@sourceware.org>
Subject: Watchpoint prorogation to child threads
Date: Tue, 26 Feb 2008 15:14:00 -0000 [thread overview]
Message-ID: <47C42CA3.1030003@redhat.com> (raw)
A question about watchpoint prorogation to child threads:
Thread A clones/forks Thread B
In the state machine that deals with the watchpoint code, the new code
will update cloned offspring with the same set of watchpoints.
This is how I see it now. Are there useful use-cases that dictate that
this behavior should not happen?
Regards
Phil
next reply other threads:[~2008-02-26 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:14 Phil Muldoon [this message]
2008-02-26 16:00 ` Mark Wielaard
2008-02-26 16:11 ` Phil Muldoon
2008-02-26 16:25 ` Mark Wielaard
2008-02-26 16:43 ` Phil Muldoon
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=47C42CA3.1030003@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).