https://bugs.kde.org/show_bug.cgi?id=369026
Bug ID: 369026
Summary: WARNING: unhandled amd64-linux syscall: 169
Product: valgrind
Version: 3.11.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: mar...@juszkiewicz.com.pl
<<<test_start>>>
tag=reboot01_valgrind_memory_leak_check stime=1474194666
cmdline=" valgrind -q --leak-check=full --trace-children=yes reboot01"
contacts=""
analysis=exit
<<<test_output>>>
--23663-- WARNING: unhandled amd64-linux syscall: 169
--23663-- You may be able to write your own handler.
--23663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23663-- Nevertheless we consider this a bug. Please report
--23663-- it at http://valgrind.org/support/bug_reports.html.
--23663-- WARNING: unhandled amd64-linux syscall: 169
--23663-- You may be able to write your own handler.
--23663-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23663-- Nevertheless we consider this a bug. Please report
--23663-- 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=0 termination_type=exited termination_id=1 corefile=no
cutime=60 cstime=2
<<<test_end>>>
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
