All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Roland McGrath <roland@redhat.com>
Cc: "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: Thu, 15 Jun 2006 18:58:16 -0400	[thread overview]
Message-ID: <200606151900_MC3-1-C293-BD30@compuserve.com> (raw)

In-Reply-To: <20060613231000.38B76180072@magilla.sf.frob.com>

On Tue, 13 Jun 2006 16:10:00 -0700, Roland McGrath wrote:

> I have been working on for a while, and imagining for much longer,
> replacing ptrace from the ground up.  This is what I've come up with so
> far, and I'm looking for some reactions on the direction.

At least three different sets of people want to extend the syscall
tracing.  Jeff Dike posted a patch that lets you supply a bitmask of
syscalls to trace.  Renzo Davoli posted one that lets you decide, after
trapping entrance to a syscall, whether to skip the trap that would
normally be done on exit from the same call.  Charles P. Wright also
had a similar patch.  I think this needs to be done at the utrace
level -- a tracing engine couldn't add that on its own (could it?)

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.

And BTW patches 1 and 2 never made it to the list.  The ones on your
server (http://redhat.com/~roland/utrace/) don't apply cleanly due to
whitespace damage but that can be fixed by stripping trailing whitespace
from the kernel files patch(1) complains about.

-- 
Chuck

             reply	other threads:[~2006-06-15 23:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 22:58 Chuck Ebbert [this message]
2006-06-16 14:42 ` [RFC PATCH 0/4] utrace: new modular infrastructure for user debug/tracing Frank Ch. Eigler
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=200606151900_MC3-1-C293-BD30@compuserve.com \
    --to=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 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.