[Bug tapsets/17928] A number of the systemtap.syscall/syscall.exp tests fail on 32-bit arm because size_t sign extended to 64-bit value

[wcohen at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17928

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #13 from William Cohen <wcohen at redhat dot com> ---
Down to the following 32-bit arm failure and none seem to be unrelated to the
32-bit size of operands:

FAIL: 32-bit dup syscall getting wrong arg locations for dup3()
FAIL: 32-bit uid syscall getting wrong arg locations for setuid()
FAIL: 32-bit mmap syscall getting wrong arg locations for mlock()

FAIL: 32-bit fadvise64 syscall existing "foobar" in directory caused failure

FAIL: 32-bit shmat syscall shmat SHM_RDONLY op fail with -EINVAL

-- 
You are receiving this mail because:
You are the assignee for the bug.