This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17951] New: cast-user.exp regressed due to the syscall.bind tapset modification
- From: "mcermak at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 10 Feb 2015 10:27:43 +0000
- Subject: [Bug runtime/17951] New: cast-user.exp regressed due to the syscall.bind tapset modification
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17951
Bug ID: 17951
Summary: cast-user.exp regressed due to the syscall.bind tapset
modification
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
The cast-user.exp regressed on rhel[67] all arches except x86_64 and aarch64.
The cause apparently is commit 238e9406.
The testcase contains an expected output text sample. On affected platforms the
testcase now produces twice the expected output (and thus fails). This seems to
relate to commit 238e9406, where the bind syscall has been modified, so that
now it's being hit twice on affected platforms.
On x86_64 the testcase works correctly because:
=======
7.1 S x86_64 # stap -e 'probe syscall.bind { println(pp()) }' -c
/root/systemtap/testsuite/cast-user.exe
kernel.function("SyS_bind@net/socket.c:1515").call?
7.1 S x86_64 #
=======
Following is an example of the issue cause:
=======
7.1 S s390x # stap -e 'probe syscall.bind { println(pp()) }' -c
/root/systemtap/testsuite/cast-user.exe
kernel.function("SyS_socketcall@net/socket.c:2473").call?
kernel.function("SyS_bind@net/socket.c:1515").call?
7.1 S s390x #
=======
--
You are receiving this mail because:
You are the assignee for the bug.