This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/9771] New: Detecting probes classes system wide
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 21 Jan 2009 12:07:57 -0000
- Subject: [Bug translator/9771] New: Detecting probes classes system wide
- Reply-to: sourceware-bugzilla at sourceware dot org
stap -l and stap -L are great if you know what kind of probes there are and/or
which processes have markers in them. But it is not easy to figure out the probe
classes and arguments/process names without some extra knowledge.
stap -l * is a start, but doesn't get you any further:
$ stap -l \*
begin
end
error
never
Ideally stap -l without any arguments would give you the probe classes (kernel,
module, timer, process, tapset aliases, etc) timer, and given a probe class
would give you the applicable arguments (kernel -> function, statement, etc,
module -> module names, timer -> jiffies, ms, profile, etc, process -> function,
argument, mark, etc, process.mark -> processes on system containing markers, etc.)
For processes and libraries with markers compiled in it makes sense to have a
system wide registry (directory?) where marker files can be placed describing
the process and the mark semantics (plus arguments).
--
Summary: Detecting probes classes system wide
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
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.