From: Chris Dunlop <chris@onthe.net.au>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Can't set statement probe in self-built linux-4.4
Date: Thu, 30 Jun 2016 22:34:00 -0000 [thread overview]
Message-ID: <20160630223410.GB16787@onthe.net.au> (raw)
In-Reply-To: <y0mk2h6vi3c.fsf@fche.csb>
Hi Frank,
On Thu, Jun 30, 2016 at 10:58:47AM -0400, Frank Ch. Eigler wrote:
>> [...]
>> I can't seem to set statement probes in a self-built linux-4.4. What can
>> be going wrong? [...]
[...]
> Have you tried:
>
> $ stap -L 'kernel.statement("register_shrinker@*:*")'
>
> to get the list of line numbers that systemtap recognizes?
No, I hadn't come across that option in my travels - that's useful!
Unfortunately it doesn't come back with anything:
$ stap -v -L 'kernel.statement("register_shrinker@*:*")'
Pass 1: parsed user script and 116 library scripts using 93372virt/31140res/3000shr/28456data kb, in 190usr/20sys/206real ms.
Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using 131260virt/69116res/3764shr/66344data kb, in 310usr/40sys/354real ms.
$
next prev parent reply other threads:[~2016-06-30 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 7:58 Chris Dunlop
2016-06-30 14:58 ` Frank Ch. Eigler
2016-06-30 22:34 ` Chris Dunlop [this message]
2016-07-01 16:12 ` David Smith
2016-07-01 20:44 ` Chris Dunlop
[not found] ` <20160701034302.GA23357@onthe.net.au>
2016-07-04 20:55 ` Chris Dunlop
2016-07-14 16:08 ` Chris Dunlop
2016-07-14 16:55 ` David Smith
2016-07-14 17:27 ` Chris Dunlop
2016-07-14 18:23 ` David Smith
2016-07-14 17:21 ` Josh Stone
2016-07-14 17:30 ` Chris Dunlop
2016-07-14 23:19 ` Chris Dunlop
2016-07-15 13:57 ` David Smith
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=20160630223410.GB16787@onthe.net.au \
--to=chris@onthe.net.au \
--cc=fche@redhat.com \
--cc=systemtap@sourceware.org \
/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).