This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/6711] New: need script syntax for extending blacklist
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 30 Jun 2008 23:02:03 -0000
- Subject: [Bug translator/6711] New: need script syntax for extending blacklist
- Reply-to: sourceware-bugzilla at sourceware dot org
When we find another unsafe-to-probe region, it is inconvenient to
recompile the translator just to add a line to the blacklist regexps.
It would be nice if there was a syntax for adding blacklist entries
on the fly, as a part of the tapset or even separately distributed
as an emergency fix.
A syntax like this would avoid new tokens:
~ probe PROBEPOINT
A possible implementation would be to resolve PROBEPOINT to a
derived_probe as usual (assuming an empty handler), but would
submit it specially to the derived_probe_group. When it's time
to emit all the probes into C code, the derived_probe_group
could look for an intersection between the two sets, and spit
out an error.
(Using the existing alias mechanism:
probe SOMETHING.BLACKLISTED = never { $trigger_an_error = 0 }
would not work since wildcards can't appear on the LHS.)
--
Summary: need script syntax for extending blacklist
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6711
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.