From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/24448] New: exelib.exp regressed on rhel8
Date: Thu, 11 Apr 2019 14:07:00 -0000 [thread overview]
Message-ID: <bug-24448-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24448
Bug ID: 24448
Summary: exelib.exp regressed on rhel8
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 11740
--> https://sourceware.org/bugzilla/attachment.cgi?id=11740&action=edit
test logs
The exelib.exp testcase regressed comparing rhel-7 and rhel-8. The test only
runs with -O3 by default. Re-running it with -O0 showed some failures, and
with -O0 the test passed.
The first failure I see (with the default -O3) is:
=======
8.0 Server x86_64 # gcc
/usr/share/systemtap/testsuite/systemtap.exelib/uprobes_lib.c
-isystem/usr/share/systemtap/testsuite -isystem/usr/include -g -m32 -O3 -fPIC
-shared -lm -o ./libuprobeslibgcc-O3-m32-debug.so
8.0 Server x86_64 # gcc
/usr/share/systemtap/testsuite/systemtap.exelib/uprobes_exe.c
-isystem/usr/share/systemtap/testsuite -isystem/usr/include -g -m32 -O3 -L.
-luprobeslibgcc-O3-m32-debug -Wl,-rpath,. -lm -o
./uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe
8.0 Server x86_64 # stap -w --ldd
/usr/share/systemtap/testsuite/systemtap.exelib/libmarkunamestack.stp
./uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe
./libuprobeslibgcc-O3-m32-debug.so -c
./uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe
main
exe: main=main
main_func: 3
exe: main_func=main_func
print_ubacktrace exe 0
0x8048580 : main_func+0x0/0x50
[...yeyJV/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
0x8048422 : main+0x22/0x40
[...yeyJV/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
main_count: 3
main_func: 2
exe: main_func=main_func
print_usyms exe 1
0x8048580 : main_func+0x0/0x50
[...yeyJV/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
0x80485a7 : main_func+0x27/0x50
[...yeyJV/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
0x8048422 : main+0x22/0x40
[...yeyJV/uprobesgcc-O3-m32-debug-uprobeslibgcc-O3-m32-debug_exe]
main_count: 2
main_func: 1
exe: main_func=main_func
main_count: 1
lib_main
lib: lib_main=lib_main
lib_func: 3
lib: lib_func=lib_func
print_ubacktrace lib 2
0xf7fc1480 : lib_func+0x0/0x50
[/tmp/tmp.98qTgyeyJV/libuprobeslibgcc-O3-m32-debug.so]
0xf7fc14f0 : lib_main+0x20/0x2c
[/tmp/tmp.98qTgyeyJV/libuprobeslibgcc-O3-m32-debug.so]
func_count: 5360
^^^^^^^^^^^^^^^^^^ HERE the hitcount should be 3
Pass 5: run failed. [man error::pass5]
(1) 8.0 Server x86_64 #
=======
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-11 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 14:07 mcermak at redhat dot com [this message]
2019-04-11 14:08 ` [Bug runtime/24448] " mcermak at redhat dot com
2019-04-11 14:10 ` 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-24448-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).