From: Arkady <arkady.miasnikov@gmail.com>
To: Adam Guderski <a.guderski@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: Problem with vfs probe on Proxmox kernel
Date: Thu, 26 Jan 2017 04:51:00 -0000 [thread overview]
Message-ID: <CANA-60p62NN0pODDv-KLVBgu6MQu0Q3tgj9Y39u4zjrTzTDcEQ@mail.gmail.com> (raw)
In-Reply-To: <13b0aebd-4bbe-f0ca-bf30-1605da0097f5@gmail.com>
I am running
Systemtap translator/driver (version 2.9/0.165, Debian version
2.9-2ubuntu2 (xenial))
on
Linux ubuntu 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
and vfsread/vfswrite work fine.
On Thu, Jan 26, 2017 at 12:44 AM, Adam Guderski <a.guderski@gmail.com> wrote:
> Hello,
>
> I've got problem running sample traceio.stp script (obtained from
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/SystemTap_Beginners_Guide/#traceio2)
> on Proxmox VE 4.4 system. Proxmox is a Debian-based Linux distro which
> uses a custom Ubuntu-based kernel. The Proxmox repository does not
> provide a kernel with debug symbols, so I had to compile it from
> provided sources - version 4.4.35-2-pve, to be specific. Debian repos
> (jessie) provide systemtap in version 2.9, which from what I read does
> not support 4.4 kernels, so I compiled systemtap from sources (from
> master branch, version 3.1/0.159).
>
> With such setup, I'm able to run sample "hello world" stap script and
> couple of others, but all scripts with vfs probes fail. I attach full
> verbose (-vvv) output here: http://pastebin.com/DiWMsrtr, but I think
> the main error can be explained below. What can I do about it? I
> searched for couple of hours but did not find anything that would help.
>
> Best regards,
> Adam
>
>
> # stap -v traceio2.stp 0xfb00
> Pass 1: parsed user script and 119 library scripts using
> 71608virt/43716res/4464shr/39904data kb, in 140usr/0sys/132real ms.
> semantic error: while resolving probe point: identifier 'kernel' at
> /usr/local/share/systemtap/tapset/linux/vfs.stp:987:19
> source: probe vfs.write = kernel.function("vfs_write")
> ^
>
> semantic error: missing x86_64 kernel/module debuginfo [man
> warning::debuginfo] under '/lib/modules/4.4.35-2-pve/build'
>
> semantic error: resolution failed in alias expansion builder
>
> semantic error: while resolving probe point: identifier 'vfs' at
> traceio2.stp:14:7
> source: probe vfs.write, vfs.read
> ^
>
> semantic error: no match
>
> semantic error: while resolving probe point: identifier 'kernel' at
> /usr/local/share/systemtap/tapset/linux/vfs.stp:915:18
> source: probe vfs.read = kernel.function("vfs_read")
> ^
>
> semantic error: missing x86_64 kernel/module debuginfo [man
> warning::debuginfo] under '/lib/modules/4.4.35-2-pve/build'
>
> semantic error: resolution failed in alias expansion builder
>
> semantic error: while resolving probe point: identifier 'vfs' at
> traceio2.stp:14:18
> source: probe vfs.write, vfs.read
> ^
>
> semantic error: no match
>
> Pass 2: analyzed script: 1 probe, 33 functions, 1 embed, 1 global using
> 72384virt/46080res/6016shr/40680data kb, in 40usr/100sys/146real ms.
> Pass 2: analysis failed. [man error::pass2]
next prev parent reply other threads:[~2017-01-26 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 22:44 Adam Guderski
2017-01-26 4:51 ` Arkady [this message]
2017-01-26 17:38 ` David Smith
2017-01-26 18:43 ` Adam Guderski
2017-01-26 19:05 ` David Smith
2017-01-26 21:27 ` Adam Guderski
2017-01-26 21:34 ` David Smith
2017-01-26 21:52 ` Adam Guderski
2017-01-26 22:41 ` David Smith
2017-01-27 2:04 ` Adam Guderski
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=CANA-60p62NN0pODDv-KLVBgu6MQu0Q3tgj9Y39u4zjrTzTDcEQ@mail.gmail.com \
--to=arkady.miasnikov@gmail.com \
--cc=a.guderski@gmail.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).