From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24358] New: 32-bit stapbpf: could not find _stext in /proc/kallsyms
Date: Mon, 18 Mar 2019 15:28:00 -0000 [thread overview]
Message-ID: <bug-24358-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24358
Bug ID: 24358
Summary: 32-bit stapbpf: could not find _stext in
/proc/kallsyms
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: ---
Host: Linux stap-f28-32.local 4.20.5-100.fc28.i686 #1 SMP Mon Jan 28 19:34:15
UTC 2019 i686 i686 i386 GNU/Linux
Snapshot: version 4.1/0.174, commit release-4.0-97-g6b0430b6b2ba
Also seen on kernel 4.18.16, f29
spawn stap -v --runtime=bpf
/notnfs/smakarov/stap-checkout/testsuite/systemtap.bpf/bpf_tests/array.stp
Pass 1: parsed user script and 49 library scripts using
31736virt/16064res/7212shr/8832data kb, in 20usr/0sys/40real ms.
Pass 2: analyzed script: 5 probes, 3 functions, 0 embeds, 1 global using
64872virt/50208res/8168shr/41968data kb, in 1450usr/50sys/1$
Pass 4: compiled BPF into "stap_4963.bo" in 0usr/0sys/4real ms.
Pass 5: starting run.
Error loading /tmp/stap130KEQ/stap_4963.bo: could not find _stext in
/proc/kallsymsWARNING: /notnfs/smakarov/stap-checkout/stap_inst$
Pass 5: run completed in 10usr/70sys/94real ms.
Pass 5: run failed. [man error::pass5]
Executing: kill -INT -4963
Probably related to pr21891
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-03-18 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:28 me at serhei dot io [this message]
2019-03-18 16:09 ` [Bug bpf/24358] 32-bit stapbpf: things need fixing re: (void *) use in libbpf and elsewhere 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-24358-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).