From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7337 invoked by alias); 10 Feb 2010 02:10:49 -0000 Received: (qmail 7300 invoked by uid 48); 10 Feb 2010 02:10:37 -0000 Date: Wed, 10 Feb 2010 02:10:00 -0000 Message-ID: <20100210021037.7299.qmail@sourceware.org> From: "jistone at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20080630230203.6711.fche@redhat.com> References: <20080630230203.6711.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/6711] need script syntax for extending blacklist X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00368.txt.bz2 ------- 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.