public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mwielaard@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	systemtap@sources.redhat.com,         utrace-devel@redhat.com
Subject: Re: external systemtap meeting notes 20070816
Date: Fri, 28 Sep 2007 16:14:00 -0000	[thread overview]
Message-ID: <1190968614.3866.10.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20070926203356.F26164D04B7@magilla.localdomain>

On Wed, 2007-09-26 at 13:33 -0700, Roland McGrath wrote:
> > Would this hack work: have the second utrace engine refuse to put a
> > breakpoint wherever it suspects another engine may have put one?  
> 
> Sure, it's easy to notice the breakpoint instruction already there.

Would the second engine then also get an event notification when the
existing breakpoint gets hit? If so then it would be nice to have a
mechanism to detect a breakpoint being removed so an engine could say
"wait! I am still interested in monitoring when that address gets hit,
please keep that breakpoint there", and then just have the first engine
not be notified of any breakpoint events anymore, and only notify the
second engine from then on. (This is kind of what we do in Frysk, but
there of course we do all breakpoint handling in user space through one
ptrace wait monitoring thread that dispatches the events, so we are in
control of all breakpoint setting and breakpoint hit event detection.)

Cheers,

Mark

      reply	other threads:[~2007-09-28  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8592.1187789486.29635.external-perftools-list@redhat.com>
     [not found] ` <y0mlkc3k23c.fsf@ton.toronto.redhat.com>
     [not found]   ` <mailman.3771.1188945116.11517.external-perftools-list@redhat.com>
2007-09-05  6:15     ` Frank Ch. Eigler
2007-09-26 12:01       ` Roland McGrath
2007-09-26 13:54         ` Frank Ch. Eigler
2007-09-26 23:44           ` Roland McGrath
2007-09-28 16:14             ` Mark Wielaard [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=1190968614.3866.10.camel@dijkstra.wildebeest.org \
    --to=mwielaard@redhat.com \
    --cc=fche@redhat.com \
    --cc=roland@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=utrace-devel@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).