<<<test_start>>> tag=reboot01_valgrind_memory_leak_check stime=1473973971 cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01" contacts="" analysis=exit <<<test_output>>> --24614-- WARNING: unhandled arm64-linux syscall: 142 --24614-- You may be able to write your own handler. --24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --24614-- Nevertheless we consider this a bug. Please report --24614-- it at http://valgrind.org/support/bug_reports.html. --24614-- WARNING: unhandled arm64-linux syscall: 142 --24614-- You may be able to write your own handler. --24614-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --24614-- Nevertheless we consider this a bug. Please report --24614-- it at http://valgrind.org/support/bug_reports.html. reboot01 1 TFAIL : reboot01.c:109: reboot(2) Failed for option LINUX_REBOOT_CMD_CAD_ON reboot01 2 TFAIL : reboot01.c:109: reboot(2) Failed for option LINUX_REBOOT_CMD_CAD_OFF <<<execution_status>>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=44 cstime=2 <<<test_end>>> Reproducible: Always
https://bugs.kde.org/show_bug.cgi?id=369026 - same for amd64
Can we close it? IIRC it was merged into valgrind.
https://bugs.kde.org/show_bug.cgi?id=369026 This has only been implemented (partially) for MIPS.