From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/24224] New: tapsets.cxx Assert kernel relocation invariants fails for some kernel.function("*@*.c:*") probes
Date: Fri, 15 Feb 2019 21:06:00 -0000 [thread overview]
Message-ID: <bug-24224-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24224
Bug ID: 24224
Summary: tapsets.cxx Assert kernel relocation invariants fails
for some kernel.function("*@*.c:*") probes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
On Fedora rawhide (kernel-5.0.0-0.rc6.git1.1.fc30.x86_64) a couple of the
systemtap examples whythefail.stp and varwatch.stp tests runs probe
kernel.statement("kernel_function"@file.c:*"). The scripts fail to run due to
tapsets.cxx throwing the error:
inconsistent relocation address
Below is the parts of the systemtap.log with the failures:
PRETEST PWD=/usr/share/systemtap/testsuite
meta taglines '' tag 'test_support' value ''
TEST PWD=/usr/share/systemtap/testsuite/systemtap.examples/general
meta taglines 'test_check: stap -wp4 varwatch.stp
'kernel.statement("do_sys_open@fs/open.c:*")' '$$vars'' tag 'test_check' value
'stap -wp4 varwatch.stp 'kernel.statement("do_sys_open@fs/open.c:*")' '$$vars''
attempting command stap -wp4 varwatch.stp
'kernel.statement("do_sys_open@fs/open.c:*")' '$$vars'
OUT semantic error: inconsistent relocation address: keyword at
varwatch.stp:5:1
source: probe $1 {
^
Pass 2: analysis failed. [man error::pass2]
Number of similar error messages suppressed: 14.
Rerun with -v to see them.
child process exited abnormally
RC 1
FAIL: systemtap.examples/general/varwatch build
PRETEST PWD=/usr/share/systemtap/testsuite
meta taglines '' tag 'test_support' value ''
TEST PWD=/usr/share/systemtap/testsuite/systemtap.examples/general
meta taglines 'test_check: stap -p4 whythefail.stp kernel do_sys_open '$return
< 0'' tag 'test_check' value 'stap -p4 whythefail.stp kernel do_sys_open
'$return < 0''
attempting command stap -p4 whythefail.stp kernel do_sys_open '$return < 0'
OUT semantic error: inconsistent relocation address: keyword at
whythefail.stp:37:1
source: probe $1 . statement(@2 "@*:*") {
^
Pass 2: analysis failed. [man error::pass2]
Number of similar error messages suppressed: 14.
Rerun with -v to see them.
child process exited abnormally
RC 1
FAIL: systemtap.examples/general/whythefail build
The linetime example is also using a 'kernel.statement("do_nanosleep@*:*")',
but that does not trigger the error and the test passes. It looks like
something is going wrong in the assert tests for the code below (some
diagnostic prints showed that the section was "_stext" rather than "" for a run
of varwatch.stp:
// Assert kernel relocation invariants
if (section == "" && dwfl_addr != addr) // addr should be absolute
throw SEMANTIC_ERROR (_("missing relocation basis"), tok);
if (section != "" && dwfl_addr == addr) // addr should be an offset
throw SEMANTIC_ERROR (_("inconsistent relocation address"), tok);
}
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-02-15 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:06 wcohen at redhat dot com [this message]
2019-02-15 21:33 ` [Bug translator/24224] " wcohen at redhat dot com
2019-02-22 21:58 ` wcohen at redhat dot com
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@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).