From: Mark Wielaard <mark@klomp.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Watchpoint prorogation to child threads
Date: Tue, 26 Feb 2008 16:00:00 -0000 [thread overview]
Message-ID: <1204041610.3487.62.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <47C42CA3.1030003@redhat.com>
Hi Phil,
On Tue, 2008-02-26 at 15:13 +0000, Phil Muldoon wrote:
> 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?
It would be nice if this is similar to the breakpoints. Low-level
breakpoints are the same on a clone (because they are really just
markers in the code segment which is the same), but they are cleared on
exec (because then the memory of the process is reset).
Cheers,
Mark
next prev parent reply other threads:[~2008-02-26 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:14 Phil Muldoon
2008-02-26 16:00 ` Mark Wielaard [this message]
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=1204041610.3487.62.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=pmuldoon@redhat.com \
/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).