From: Daniel Jacobowitz <dan@debian.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
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: Wed, 21 Jun 2006 09:49:18 -0400 [thread overview]
Message-ID: <20060621134918.GA1361@nevyn.them.org> (raw)
In-Reply-To: <y0mlkrxupqf.fsf@ton.toronto.redhat.com>
On Fri, Jun 16, 2006 at 10:42:00AM -0400, Frank Ch. Eigler wrote:
> 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?
FYI: I talked with Roland about this a while ago, and got the
impression that he was interested in implementing it, but wanted to get
utrace going first. It doesn't really relate to utrace; but it would
need a new interface however it was implemented.
GDB really does crave this feature.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-21 13:53 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
2006-06-21 13:49 ` Daniel Jacobowitz [this message]
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=20060621134918.GA1361@nevyn.them.org \
--to=dan@debian.org \
--cc=76306.1226@compuserve.com \
--cc=blaisorblade@yahoo.it \
--cc=cwright@cs.sunysb.edu \
--cc=fche@redhat.com \
--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 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.