public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/26234] utrace_derived_probes (and others?) being silently ignored by bpf backend
Date: Tue, 21 Jul 2020 15:10:24 +0000	[thread overview]
Message-ID: <bug-26234-6586-iv8bRfubEp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26234-6586@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
40dbe72afa2 adds warnings for the other probe types
though in some cases they may still be overridden by earlier, more confusing
warnings

e.g. 
sudo stap --bpf -ve 'probe process("/bin/ls").insn { println("hello") exit() }'

Pass 1: parsed user script and 51 library scripts using
40640virt/23544res/9372shr/13872data kb, in 0usr/0sys/7real ms.
semantic error: while resolving probe point: identifier 'process' at
<input>:1:7
        source: probe process("/bin/ls").insn { println("hello", execname(),
pid()) }
                      ^

semantic error: while resolving probe point: identifier 'process' at :1:7
        source: probe process("/bin/ls").insn { println("hello", execname(),
pid()) }
                      ^

semantic error: process probes not available without kernel CONFIG_UTRACE

Pass 2: analyzed script: 0 probes, 0 functions, 0 embeds, 0 globals using
40640virt/23544res/9372shr/13872data kb, in 0usr/0sys/0real ms.
Pass 2: analysis failed.  [man error::pass2]

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

      parent reply	other threads:[~2020-07-21 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 15:00 [Bug bpf/26234] New: " me at serhei dot io
2020-07-13 17:39 ` [Bug bpf/26234] " me at serhei dot io
2020-07-21 15:10 ` me at serhei dot io [this message]

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-26234-6586-iv8bRfubEp@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).