<<<test_start>>> tag=setdomainname01_valgrind_memory_leak_check stime=1473974763 cmdline=" valgrind -q --leak-check=full --trace-children=yes setdomainname01" contacts="" analysis=exit <<<test_output>>> --26022-- WARNING: unhandled arm64-linux syscall: 162 --26022-- You may be able to write your own handler. --26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --26022-- Nevertheless we consider this a bug. Please report --26022-- it at http://valgrind.org/support/bug_reports.html. --26022-- WARNING: unhandled arm64-linux syscall: 162 --26022-- You may be able to write your own handler. --26022-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --26022-- Nevertheless we consider this a bug. Please report --26022-- it at http://valgrind.org/support/bug_reports.html. setdomainname01 1 TFAIL : setdomainname01.c:104: setdomainname() Failed, errno = 38 : Function not implemented setdomainname01 0 TWARN : setdomainname01.c:146: setdomainname() failed while restoring domainname to "(none)" <<<execution_status>>> initiation_status="ok" duration=0 termination_type=exited termination_id=5 corefile=no cutime=54 cstime=2 <<<test_end>>> Reproducible: Always
https://bugs.kde.org/show_bug.cgi?id=369030 - same for amd64
Can we close it? IIRC it was merged into valgrind.
Same as for https://bugs.kde.org/show_bug.cgi?id=369030 This has only been implemented for MIPS (but it doesn't do any checks on the supplied name)