[Bug translator/5898] adapt stap -c for user probes
jkenisto at us dot ibm dot com
sourceware-bugzilla@sourceware.org
Tue Mar 11 16:44:00 GMT 2008
------- Additional Comments From jkenisto at us dot ibm dot com 2008-03-11 16:43 -------
(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.
>
> 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.
>
> In terms of what I'm working on, I think your requested feature becomes:
> 1. use utrace to watch the pid of the shell (instead of the entire system)
> 2. look for the exec of 'pgm'
> 3. attach the user utrace/uprobes probes to the newly created 'pgm'
>
> Is this what you are looking for?
Yes.
--
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.
More information about the Systemtap
mailing list