Can't set statement probe in self-built linux-4.4
Chris Dunlop
chris@onthe.net.au
Mon Jul 4 20:55:00 GMT 2016
On Thu, Jun 30, 2016 at 05:57:44PM +1000, Chris Dunlop wrote:
> Hi,
>
> I can't seem to set statement probes in a self-built linux-4.4. What can
> be going wrong?
Apologies for being a pest, but any ideas?
Chris
On Fri, Jul 01, 2016 at 01:43:02PM +1000, Chris Dunlop wrote:
> On Thu, Jun 30, 2016 at 08:57:38PM -0400, Frank Ch. Eigler wrote:
>> Something's weird about your -vvvvv trace too; a similar command
>> that works here gives a lot more "function cache ...." type lines.
>>
>> Any chance you could tar.xz up the whole vmlinux build tree?
>
> Of course: https://www.dropbox.com/s/l7cvs773mw8jqga/build.tar.xz?dl=0 (193M)
>
> Chris
On Sat, Jul 02, 2016 at 06:44:28AM +1000, Chris Dunlop wrote:
> On Fri, Jul 01, 2016 at 11:11:54AM -0500, David Smith wrote:
>> On 06/30/2016 05:34 PM, Chris Dunlop wrote:
>>>
>>> $ 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.
>>
>> Hmm. Please try the following:
>>
>> # stap -L 'kernel.function("register_shrinker").*'
>
> $ stap -L 'kernel.function("register_shrinker").*'
> kernel.function("register_shrinker").call
> kernel.function("register_shrinker").exported
> kernel.function("register_shrinker").return
>
>> That should let us know if 'register_shrinker' is only inlined in your
>> kernel.
More information about the Systemtap
mailing list