This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6897] stap should assert valid PIDs for process(PID) probes
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 17 Sep 2008 13:48:15 -0000
- Subject: [Bug runtime/6897] stap should assert valid PIDs for process(PID) probes
- References: <20080917112256.6897.srikar@linux.vnet.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-09-17 13:48 -------
I changed the summary line to better reflect the concern.
If this was desirable (I'm unsure), it could be done by
running a test after the task_finder_start work that looks
through all utrace (+ uprobe) probe point specs. Any
pid-filtered ones that have not become activated could
be treated as a cause for a startup error.
OTOH, we silently permit module("foo") probes where the
foo module is not actually loaded at run time.
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|stap not resolving |stap should assert valid
|process(pid).statements |PIDs for process(PID) probes
|properly. |
http://sourceware.org/bugzilla/show_bug.cgi?id=6897
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.