This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/16207] New: on rawhide, we're getting more syscall.exp failures
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 22 Nov 2013 19:04:19 +0000
- Subject: [Bug tapsets/16207] New: on rawhide, we're getting more syscall.exp failures
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16207
Bug ID: 16207
Summary: on rawhide, we're getting more syscall.exp failures
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
On rawhide (3.13.0-0.rc0.git10.1.fc21.x86_64), we're getting lots of failures:
=====
Running ../../src/testsuite/systemtap.syscall/syscall.exp ...
FAIL: 64-bit access syscall
FAIL: 64-bit chmod syscall
FAIL: 64-bit dup syscall
FAIL: 64-bit inotify syscall
FAIL: 64-bit link syscall
FAIL: 64-bit net1 syscall
FAIL: 64-bit pipe syscall
FAIL: 32-bit access syscall
FAIL: 32-bit chmod syscall
FAIL: 32-bit dup syscall
FAIL: 32-bit inotify syscall
FAIL: 32-bit link syscall
FAIL: 32-bit mount syscall
FAIL: 32-bit pipe syscall
FAIL: 32-bit readwrite syscall
FAIL: 32-bit signalfd syscall
FAIL: 32-bit trunc syscall
=====
>From looking at the log file, it appears that some system calls that use to be
wrappers around other syscalls (like access() used to be a wrapper around
faccessat()) have been changed to no longer do that.
I'm sure similar errors occur in the nd_syscall.exp testcase
The solution that I've started implementing for bug #15219 (the use of
@__syscall_gate() macro), should help here.
--
You are receiving this mail because:
You are the assignee for the bug.