Bug 392118

Summary: unhandled amd64-linux syscall: 332 (statx) [KDE executables]
Product: [Developer tools] valgrind Reporter: Kevin <kjslag>
Component: generalAssignee: Julian Seward <jseward>
Status: RESOLVED FIXED    
Severity: normal CC: gareth-anthony-hulse, khalil.fazal, kjslag, maandree, mark, philippe.waroquiers
Priority: NOR    
Version: 3.13.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Linux: add sys_statx

Description Kevin 2018-03-21 04:54:04 UTC 
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.
Comment 1 Mark Wielaard 2018-03-21 11:39:43 UTC 
> --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
Comment 2 Mattias Andrée 2018-06-02 15:53:12 UTC 
Created attachment 113016 [details]
Linux: add sys_statx
Comment 3 Philippe Waroquiers 2018-08-01 20:30:50 UTC 
IMO, this bug should be fixed for the release ...
Comment 4 Philippe Waroquiers 2018-08-11 14:04:54 UTC 
Pushed as 8bc2b6fd26070f9f4d3f067910eb3e3b5e662fd7
(with a regression test (somewhat) testing stat and statx).

Thanks for the patch.
Comment 5 Paul Floyd 2022-09-02 14:39:35 UTC 
*** Bug 396369 has been marked as a duplicate of this bug. ***