From: fche@redhat.com (Frank Ch. Eigler)
To: Roland McGrath <roland@redhat.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
"Charles P. Wright" <cwright@cs.sunysb.edu>,
Renzo Davoli <renzo@cs.unibo.it>,
linux-kernel <linux-kernel@vger.kernel.org>,
Blaisorblade <blaisorblade@yahoo.it>,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [RFC PATCH 0/4] utrace: new modular infrastructure for user debug/tracing
Date: 16 Jun 2006 10:42:00 -0400 [thread overview]
Message-ID: <y0mlkrxupqf.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <200606151900_MC3-1-C293-BD30@compuserve.com>
Chuck Ebbert <76306.1226@compuserve.com> writes:
> [...] Renzo Davoli also posted a patch to allow "batching" of
> ptrace requests and Systemptap really needs this, too. AFAICT this
> can be done by writing a custom engine. [...]
Indeed, I like what I see (at least those parts I understand) in
roland's utrace code. One missed opportunity bit appears to be any
new support for something like per-thread breakpoints.
If I correctly understand how gdb etc. work, a hit breakpoint involves
stoppage of all other threads of a process, then the breakpoint
instruction is replaced by the original one, then the thread is
single-stepped, then the breakpoint is put back, then finally all
threads are resumed. Could utrace API provide short-lived per-thread
page copies to execute the single-stepped original instruction out of,
and avoid stopping & resuming all other threads?
- FChE
next prev parent reply other threads:[~2006-06-16 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 22:58 [RFC PATCH 0/4] utrace: new modular infrastructure for user debug/tracing Chuck Ebbert
2006-06-16 14:42 ` Frank Ch. Eigler [this message]
2006-06-21 13:49 ` Daniel Jacobowitz
2006-06-19 10:35 ` Roland McGrath
-- strict thread matches above, loose matches on Subject: below --
2006-06-19 4:44 Albert Cahalan
2006-06-13 23:10 Roland McGrath
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=y0mlkrxupqf.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=76306.1226@compuserve.com \
--cc=blaisorblade@yahoo.it \
--cc=cwright@cs.sunysb.edu \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=renzo@cs.unibo.it \
--cc=roland@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