This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/9771] Detecting probes classes system wide
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 17 Feb 2009 15:04:46 -0000
- Subject: [Bug translator/9771] Detecting probes classes system wide
- References: <20090121120757.9771.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2009-02-17 15:04 -------
> stap -l and stap -L are great if you know what kind of probes there are and/or
> which processes have markers in them.
We should support globbing on the process parameter (process("/bin/*")....)
to make this easier.
> Ideally stap -l without any arguments would give you the probe classes
More concretely, -l could work by traversing the match_node tree in addition
or instead of making a -p2 run via a synthetic probe script fragment. The
latter would still be necessary for wildcards that are *inside* probe point
arguments -- kernel.function("*"). For wildcards outside, traversing the
match_node tree should be fine. (I would probably avoid allowing '-l' to
have an optional parameter, for compatibility with current parsing.)
The various combinations should be enumerated here for analysis to decide
on the best mechanism.
> For processes and libraries with markers compiled in it makes sense to have a
> system wide registry (directory?) where marker files can be placed
This doesn't sound that practical. Would process path globbing as above
be sufficient?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9771
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.