From: fche@redhat.com (Frank Ch. Eigler)
To: Nan Xiao <xiaonan830818@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: How does stap execute probe aliases?
Date: Fri, 20 Nov 2015 16:12:00 -0000 [thread overview]
Message-ID: <y0mh9kgodj3.fsf@fche.csb> (raw)
In-Reply-To: <CA+MhoaPAiF2zf6J=3bCP=5Dtc=60T0+_igCSZk7028kTua0y8g@mail.gmail.com> (Nan Xiao's message of "Fri, 20 Nov 2015 17:59:47 +0800")
xiaonan830818 wrote:
> I try to execute the following script from this page
> (https://sourceware.org/systemtap/SystemTap_Beginners_Guide/targetavailable.html#available):
> [...]
> Why can't the stap find the probes? Thanks in advance!
Because that script defines aliases only (kind of like a #define FOO BAR
in a C program), and doesn't instantiate them (FOO in a C program).
So add
probe vm.pagefault { /* ... */ }
to your script.
- FChE
next prev parent reply other threads:[~2015-11-20 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 9:59 Nan Xiao
2015-11-20 16:12 ` Frank Ch. Eigler [this message]
2015-11-21 9:06 ` Nan Xiao
2015-11-21 12:55 ` Frank Ch. Eigler
2015-11-23 1:49 ` Nan Xiao
2015-11-23 1:51 ` Frank Ch. Eigler
2015-11-23 2:01 ` Nan Xiao
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=y0mh9kgodj3.fsf@fche.csb \
--to=fche@redhat.com \
--cc=systemtap@sourceware.org \
--cc=xiaonan830818@gmail.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).