From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/28285] New: Allow stapbpf backend to handle $arg1, $arg2, ...
Date: Fri, 27 Aug 2021 19:50:18 +0000 [thread overview]
Message-ID: <bug-28285-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28285
Bug ID: 28285
Summary: Allow stapbpf backend to handle $arg1, $arg2, ...
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
The stapbpf backend doesn't handle $argn (for example $arg2 in
gmalloc_watch.stp example below). A number of the tapsets use $argn to access
values passed into functions. The bpf backend should be able to access those
simple arguments also, but currently it fails. This can be demonstrated with
some of the systemtap examples:
$ sudo dnf install glib2-devel
$ cd /usr/share/systemtap/testsuite/systemtap.examples/
$ sudo stap --bpf apps/gmalloc_watch.stp -T 1
semantic error: unhandled statement or expression type: identifier '$arg2' at
/usr/share/systemtap/tapset/x86_64/libglib-2.0.so.0.6800.4.stp:31:13
source: n_bytes = $arg2;
^
Pass 4: compilation failed. [man error::pass4]
$ sudo stap --bpf apps/stap_time.stp
semantic error: unhandled statement or expression type: identifier '$arg1' at
/usr/share/systemtap/tapset/stap_staticmarkers.stp:18:12
source: session = $arg1
^
Pass 4: compilation failed. [man error::pass4]
On the same machine the linux kernel module version things work fine:
$ sudo stap apps/gmalloc_watch.stp -T 1
g_malloc: pid=2077 n_bytes=72
$ sudo stap apps/stap_time.stp -T 1
$
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-08-27 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:50 wcohen at redhat dot com [this message]
2021-09-02 19:23 ` [Bug bpf/28285] " wcohen at redhat 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=bug-28285-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).