From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/27032] New: bpf: -c CMD option does not work
Date: Mon, 07 Dec 2020 20:47:09 +0000 [thread overview]
Message-ID: <bug-27032-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27032
Bug ID: 27032
Summary: bpf: -c CMD option does not work
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
I've noticed that stap's `-c CMD` option does not work as expected in the bpf
backend. Tested the latest master branch on Fedora 32 x86_64:
```
[agentzh@fed32-min ~/git/systemtap 0 (master)]$ cat a.c
long a = 0xdeadbeef;
int main (void) {
return 0;
}
[agentzh@fed32-min ~/git/systemtap 0 (master)]$ gcc -g a.c -o /tmp/a.out
[agentzh@fed32-min ~/git/systemtap 0 (master)]$ /opt/stap/bin/stap --bpf -c
/tmp/a.out -e 'probe process("/tmp/a.out").function("main") { warn("Hit")
exit() }'
```
The last command hangs forever which means that the `/tmp/a.out` command
specified in the `-c` option never gets traced. If I run that command in
another terminal of the same machine, then that `stap` command prints and quits
immediately:
```
[agentzh@fed32-min ~/git/systemtap 0 (master)]$ /opt/stap/bin/stap --bpf -c
/tmp/a.out -e 'probe process("/tmp/a.out").function("main") { warn("Hit")
exit() }'
WARNING: Hit
```
More info about my stap and kernel:
```
[agentzh@fed32-min ~/git/systemtap 130 (master)]$ /opt/stap/bin/stap -V
Systemtap translator/driver (version 4.5/0.182, commit
release-4.4-24-g3e0d449fe427 + changes)
Copyright (C) 2005-2020 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 5.10.0-rc
enabled features: BPF NLS
[agentzh@fed32-min ~/git/systemtap 0 (master)]$ cat /proc/version
Linux version 5.9.11-100.fc32.x86_64
(mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 10.2.1 20201016 (Red
Hat 10.2.1-6), GNU ld version 2.34-6.fc32) #1 SMP Tue Nov 24 19:16:53 UTC 2020
```
Tested the same example on Fedora 28 with an older kernel. Same thing:
```
[agentzh@glass ~/git/systemtap.new 0 (master)]$ /opt/stap/bin/stap --bpf -c
/tmp/a.out -e 'probe process("/tmp/a.out").function("main") { warn("Hit")
exit() }'
[agentzh@glass ~/git/systemtap.new 134 (master)]$ cat /proc/version
Linux version 5.0.16-100.fc28.x86_64
(mockbuild@bkernel04.phx2.fedoraproject.org) (gcc version 8.3.1 20190223 (Red
Hat 8.3.1-2) (GCC)) #1 SMP Tue May 14 18:22:28 UTC 2019
```
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-12-07 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 20:47 agentzh at gmail dot com [this message]
2021-02-04 16:31 ` [Bug bpf/27032] " 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-27032-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).