This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/6711] need script syntax for extending blacklist
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 10 Feb 2010 02:10:37 -0000
- Subject: [Bug translator/6711] need script syntax for extending blacklist
- References: <20080630230203.6711.fche@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jistone at redhat dot com 2010-02-10 02:10 -------
(In reply to comment #6)
> I am figuring out the suitable way to implement blacklist. Any suggestion
> or comments are welcome.
Maybe it's the wrong approach to fully resolve noprobes to real probe points.
If the probe builder new that it was "deriving" a noprobe, it could just save
the parameters into its dynamic blacklist patterns, without actually resolving
anything.
As each real probe is resolved, they can just be pattern-matched against globs
in the blacklisted (module,function,[source,line]) tuples.
I think this way we could be just as expressive as our current regexes.
--
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.