public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24804] bpf code generation unable to determine type of target variable used to index global variable
Date: Thu, 11 Jul 2019 18:10:00 -0000	[thread overview]
Message-ID: <bug-24804-6586-bAAQbW55b5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24804-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24804

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
systemtap seems okay with target a target variable for function:

[wcohen@localhost systemtap]$ stap --bpf -L 'kernel.function("__do_sys_fcntl")'
kernel.function("__do_sys_fcntl@fs/fcntl.c:448") $arg:long unsigned int
$cmd:unsigned int $fd:unsigned int
[wcohen@localhost systemtap]$ sudo stap -v --bpf -e 'global ids; probe
kernel.function("__do_sys_fcntl"){ids[$arg]++}' -T 10
Pass 1: parsed user script and 70 library scripts using
336176virt/109212res/9160shr/100200data kb, in 190usr/30sys/220real ms.
Pass 2: analyzed script: 3 probes, 4 functions, 0 embeds, 1 global using
397828virt/172324res/10292shr/161852data kb, in 750usr/10sys/766real ms.
Pass 4: compiled BPF into "stap_6498.bo" in 0usr/0sys/3real ms.
Pass 5: starting run.
Pass 5: run completed in 0usr/0sys/10003real ms.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2019-07-11 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 17:43 [Bug bpf/24804] New: " wcohen at redhat dot com
2019-07-11 17:56 ` [Bug bpf/24804] " wcohen at redhat dot com
2019-07-11 18:10 ` wcohen at redhat dot com [this message]
2019-07-11 19:12 ` 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-24804-6586-bAAQbW55b5@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).