From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/24224] tapsets.cxx Assert kernel relocation invariants fails for some kernel.function("*@*.c:*") probes
Date: Fri, 22 Feb 2019 21:58:00 -0000 [thread overview]
Message-ID: <bug-24224-6586-Dzo59MeSDW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24224-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24224
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
A simpler reproducer that works both on f28 ppc64le and f29 x86_64:
$ uname -a
Linux rh-power-vm07.fit.vutbr.cz 4.20.8-100.fc28.ppc64le #1 SMP Wed Feb 13
12:45:56 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
$ sudo stap -p4 -e 'probe netdev.change_mac { exit() }'
semantic error: inconsistent relocation address: identifier 'netdev' at
<input>:1:7
source: probe netdev.change_mac { exit() }
^
Pass 2: analysis failed. [man error::pass2]
$ uname -a
Linux cervelo 4.20.8-200.fc29.x86_64 #1 SMP Wed Feb 13 13:08:05 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
$ stap -p4 -e 'probe netdev.change_mac { exit() }'
semantic error: inconsistent relocation address: identifier 'netdev' at
<input>:1:7
source: probe netdev.change_mac { exit() }
^
Pass 2: analysis failed. [man error::pass2]
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-02-22 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:06 [Bug translator/24224] New: " wcohen at redhat dot com
2019-02-15 21:33 ` [Bug translator/24224] " wcohen at redhat dot com
2019-02-22 21:58 ` wcohen at redhat dot com [this message]
2019-02-26 15:49 ` wcohen at redhat dot com
2019-02-26 18:44 ` wcohen at redhat dot com
2019-02-26 19:18 ` wcohen at redhat dot com
2019-02-26 19:23 ` [Bug translator/24224] tapsets.cxx kernel relocation assert fails when attempting to access some function parameters wcohen at redhat dot com
2019-03-08 16:33 ` 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-24224-6586-Dzo59MeSDW@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).