https://bugs.kde.org/show_bug.cgi?id=446401
Bug ID: 446401
Summary: unhandled series of rr-specific syscalls
Product: valgrind
Version: 3.18.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: j...@garrison.cc
Target Milestone: ---
SUMMARY
Valgrind complains about unimplemented syscalls when it encounters system calls
specific to rr (the record and replay framework)
STEPS TO REPRODUCE
1. I'm running portions of the Julia test suite under valgrind, following the
instructions at
https://docs.julialang.org/en/v1/devdocs/valgrind/#Running-the-Julia-test-suite-under-Valgrind
(for the purposes here, `all` can be replaced by a much simpler set of tests,
such as `tuple`).
OBSERVED RESULT
valgrind succeeds, but emits the following warning:
--114742-- WARNING: unhandled amd64-linux syscall: 1008
--114742-- You may be able to write your own handler.
--114742-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--114742-- Nevertheless we consider this a bug. Please report
--114742-- it at http://valgrind.org/support/bug_reports.html.
The README_MISSING_SYSCALL_OR_IOCTL document instructs me to run `grep 1008
/usr/include/asm/unistd*.h`, but this turns up nothing.
Turns out, julia is making this syscall to determine whether it is running
under rr:
https://github.com/JuliaLang/julia/blob/ed9ad60f0ce7cad38870b2bf9eede5dd7a4b706f/test/runtests.jl#L17-L20
There are a number of rr-specific syscalls that valgrind might want to either
handle, ignore, or display a *different*, more informative warning about:
https://github.com/rr-debugger/rr/blob/b8566d29a78d798d547e520fcaaa217a241430e0/src/syscalls.py#L1736-L1747
EXPECTED RESULT
No warning emitted would be ideal.
--
You are receiving this mail because:
You are watching all bug changes.
