From: "wenji dot huang at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6711] need script syntax for extending blacklist
Date: Mon, 25 Jan 2010 07:52:00 -0000 [thread overview]
Message-ID: <20100125075216.10152.qmail@sourceware.org> (raw)
In-Reply-To: <20080630230203.6711.fche@redhat.com>
------- Additional Comments From wenji dot huang at oracle dot com 2010-01-25 07:52 -------
Created an attachment (id=4553)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4553&action=view)
patch v2
According to the top words on the bug page, seems no
intention to replace current static black list, just additional
script-syntax adding entries on the fly.
Updated patch is to achieve that. Currently it only filters
dwarf_derived_probe,
easy to extend other probe types. Also Api function defined on tapset is
convenient.
$ ./stap -l 'kernel.function("sys_write*")'
kernel.function("sys_write@fs/read_write.c:390")
kernel.function("sys_writev@fs/read_write.c:714")
$ cat /tmp/noprobe.stp
noprobe kernel.function("sys_writev"), kernel.function("no_such")
probe kernel.function("sys_write*") {}
probe process("/home/wjhuang/systemtap/stap").function("main"){}
$ ./stap -wp2 /tmp/noprobe.stp
# probes
kernel.function("sys_write@fs/read_write.c:390") /* pc=_stext+0xf39f5 */ /* <-
kernel.function("sys_write*") */
process("/home/wjhuang/systemtap/stap").function("main@/home/wjhuang/systemtap/main.cxx:439")
/* pc=.absolute+0x40acd0 */ /* <-
process("/home/wjhuang/systemtap/stap").function("main") */
--
What |Removed |Added
----------------------------------------------------------------------------
Attachment #4544 is|0 |1
obsolete| |
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.
next prev parent reply other threads:[~2010-01-25 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080630230203.6711.fche@redhat.com>
2008-08-28 18:41 ` mhiramat at redhat dot com
2010-01-19 8:49 ` wenji dot huang at oracle dot com
2010-01-19 12:00 ` fche at redhat dot com
2010-01-21 3:21 ` wenji dot huang at oracle dot com
2010-01-21 20:22 ` jistone at redhat dot com
2010-01-22 5:46 ` wenji dot huang at oracle dot com
2010-01-25 7:52 ` wenji dot huang at oracle dot com [this message]
2010-02-10 2:10 ` jistone at redhat dot com
2010-02-10 2:15 ` jistone at redhat dot com
[not found] <bug-6711-6586@http.sourceware.org/bugzilla/>
2023-05-25 20:49 ` fche at redhat dot com
2023-05-31 2:01 ` libo.ch at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100125075216.10152.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).