Bug 369026

Summary:	WARNING: unhandled amd64-linux syscall: 169 (reboot)
Product:	[Developer tools] valgrind	Reporter:	Marcin Juszkiewicz <marcin>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	REPORTED ---
Severity:	normal	CC:	mark, sam, tom
Priority:	NOR
Version:	3.11.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Marcin Juszkiewicz 2016-09-19 06:43:20 UTC

<<<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

Comment 1 Marcin Juszkiewicz 2018-04-30 08:07:22 UTC

Can we close it? IIRC it was merged into valgrind.

Comment 2 Tom Hughes 2018-04-30 09:55:57 UTC

I see no sign that this has been added.

Comment 3 Mark Wielaard 2021-10-04 09:26:49 UTC

This has only been implemented (partially) for MIPS.