This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/5898] adapt stap -c for user probes
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 11 Mar 2008 17:01:28 -0000
- Subject: [Bug translator/5898] adapt stap -c for user probes
- References: <20080308003812.5898.jkenisto@us.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From dsmith at redhat dot com 2008-03-11 17:01 -------
(In reply to comment #4)
> (In reply to comment #2)
> > I've just started working on a related, yet different, feature. It is possible
> > that the feature this bug talks about could fall out from that work or be a
> > small addition to it.
> >
> > I'm work on providing the ability to do something like:
> >
> > probe process("/bin/program_of_interest").create {
> > # do something here...
> > }
> > probe process("/bin/program_of_interest").exit {
> > # do something here...
> > }
> >
> > (I'm undecided on the exact syntax, so feel free to suggest something better.)
>
> I think this will be a really useful feature. It's always been on our
> user-space-probing wish list.
>
> I wonder whether ".create" should be ".exec". In particular, the process.create
> event in the process.stp tapset refers to fork/create, while process.exec refers
> to exec.
Obviously "create" isn't the right name, since I really had in mind a probe that
gets called for UTRACE_EVENT(CLONE). Perhaps I should just call it "clone".
We'd have a separate event called "exec" for UTRACE_EVENT(EXEC).
> >
> > This will give you the capability to attach to existing or new instances of
> > /bin/program_of_interest system-wide. I'm attempting to do this just with
utrace.
>
> I'll be glad to see this. I could never figure out how to do such a thing with
> utrace, without a specific ancestor process to start with.
You attach your utrace engine to all processes (in theory at least - I haven't
got anything working yet). I'm basing my work on the utrace crash-suspend
example. Look at the exit_crash_suspend() function to see basically what I'll
be doing.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5898
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.