<<<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)
commit 2604bb753a9ff461550e0d4d0c1ebd3ab6488d6d Author: Martin Cermak <mcermak@redhat.com> Date: Fri Sep 19 09:31:39 2025 +0200 Wrap the setdomainname syscall The setdomainname() call sets the domain name to the value given in the character array name. The len argument specifies the number of bytes in name. (Thus, name does not require a terminating null byte.) Declare a setdomainname wrapper in priv_syswrap-linux.h and hook it for {amd64,arm,arm64,mips64,ppc32,ppc64,riscv64,s390x,x86}-linux using LINX_ with PRE handler in syswrap-linux.c https://bugs.kde.org/show_bug.cgi?id=369030 *** This bug has been marked as a duplicate of bug 369030 ***