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/25177] New: stap --bpf -c does not work as specified
Date: Fri, 08 Nov 2019 15:58:00 -0000	[thread overview]
Message-ID: <bug-25177-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 25177
           Summary: stap --bpf -c does not work as specified
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: bpf
          Assignee: systemtap at sourceware dot org
          Reporter: me at serhei dot io
  Target Milestone: ---

With test.stp:

probe begin {
  printf("BEGIN\n")
}

probe process("/opt/stap-master/bin/stap").function("main") {
  printf("found it\n")
  exit()
}

probe end {
  printf("END PASS\n")
}


$ sudo /opt/stap-master/bin/stap test.stp -c '/opt/stap-master/bin/stap -V'
Systemtap translator/driver (version 4.2/0.174, commit
release-4.1-100-ga8c7c8f114fa + changes)
Copyright (C) 2005-2019 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 5.1-rc2
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON2 PYTHON3
LIBRPM LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE
BEGIN
found it
END PASS

But the same invocation with --bpf does not launch the command:

$ sudo /opt/stap-master/bin/stap test.stp -c '/opt/stap-master/bin/stap -V'
--bpf
BEGIN
...

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

             reply	other threads:[~2019-11-08 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 15:58 me at serhei dot io [this message]
2021-02-04 16:31 ` [Bug bpf/25177] " wcohen at redhat dot com
2021-02-25 20:32 ` me at serhei dot io

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-25177-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).