I get an unhandled amd64-linux syscall 332 warning when I run valgrind on a KDE program. For example, all of the commands below result in the warning: valgrind /bin/konsole valgrind /bin/dolphin valgrind /bin/kwrite valgrind /bin/okular more output: $ valgrind /bin/konsole ==13964== Memcheck, a memory error detector ==13964== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==13964== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==13964== Command: /bin/konsole ==13964== --13964-- WARNING: unhandled amd64-linux syscall: 332 --13964-- You may be able to write your own handler. --13964-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --13964-- Nevertheless we consider this a bug. Please report --13964-- it at http://valgrind.org/support/bug_reports.html.
> --13964-- WARNING: unhandled amd64-linux syscall: 332 This is the new statx syscall: http://man7.org/linux/man-pages/man2/statx.2.html BTW. The following is a nice overview to map arch specific syscall numbers to syscall names: https://github.com/hrw/syscalls-table
Created attachment 113016 [details] Linux: add sys_statx
IMO, this bug should be fixed for the release ...
Pushed as 8bc2b6fd26070f9f4d3f067910eb3e3b5e662fd7 (with a regression test (somewhat) testing stat and statx). Thanks for the patch.
*** Bug 396369 has been marked as a duplicate of this bug. ***