From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30131] New: Testcase at_var_timer_profile.exp regressed
Date: Fri, 17 Feb 2023 08:27:09 +0000 [thread overview]
Message-ID: <bug-30131-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30131
Bug ID: 30131
Summary: Testcase at_var_timer_profile.exp regressed
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
Created attachment 14688
--> https://sourceware.org/bugzilla/attachment.cgi?id=14688&action=edit
test results overview
The testcase at_var_timer_profile.exp demonstrably regressed, specifically for
rhel9, see the attached overview. The test case was added as part of commit
bd1fcbad9165da8 back in 2013. Based on my bisection on rhel9, the regression
was caused by a kernel update 5.14.0-178.el9 ---> 5.14.0-178.el9.
Here's the testcase script as of today:
https://sourceware.org/git/?p=systemtap.git;a=blob;f=testsuite/systemtap.base/at_var_timer_profile.stp;h=479f74941a9fd739ea05b0d566c52d8929af7d03;hb=HEAD
Here's how the testcase works fine with 5.14.0-178.el9.x86_64
------------------------------------------------------------------
9 x86_64 # stap
/root/systemtap/testsuite/systemtap.base/at_var_timer_profile.stp -c
./at_var_timer_profile /root/build/testsuite/at_var_timer_profile
/usr/local/bin/stap:/root/build/testsuite/at_var_timer_profile:/usr/local/bin/staprun
/usr/local/bin/stap:/usr/local/bin/staprun
@var("foo", @1)->bar: 42
@var("foo@at_var_timer_profile.c", @1)->bar: 42
@var("foo@at_var_timer_profile.c", @2)->bar: 42
@var("foo", @1)$: {.bar=42}
@var("foo", @1)$$: {.bar=42}
@defined(@var("foo", "badmodle")): NO
@defined(@var("foo", @3)): NO
9 x86_64 #
Here's how the testcase fails with 5.14.0-179.el9.x86_64
------------------------------------------------------------------
9 x86_64 # stap
/root/systemtap/testsuite/systemtap.base/at_var_timer_profile.stp -c
./at_var_timer_profile /root/build/testsuite/at_var_timer_profile
/usr/local/bin/stap:/root/build/testsuite/at_var_timer_profile:/usr/local/bin/staprun
/usr/local/bin/stap:/usr/local/bin/staprun
ERROR: read fault [man error::fault] at 0x404028 near operator '@var' at
/root/systemtap/testsuite/systemtap.base/at_var_timer_profile.stp:15:42
WARNING: Number of errors: 1, skipped probes: 0
WARNING: /usr/local/bin/staprun exited with status: 1
Pass 5: run failed. [man error::pass5]
9 x86_64 #
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-02-17 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:27 mcermak at redhat dot com [this message]
2023-02-17 8:36 ` [Bug runtime/30131] " mcermak at redhat dot com
2023-02-17 8:56 ` mcermak 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-30131-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).