https://bugs.kde.org/show_bug.cgi?id=439090
Bug ID: 439090
Summary: unhandled amd64-linux syscall: 436 (close_range)
Product: valgrind
Version: unspecified
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: ojwbetts+...@gmail.com
Target Milestone: ---
The close_range syscall was added in Linux 5.9.
STEPS TO REPRODUCE
$ cat <<END > test-close_range.c
#include <sys/syscall.h>
#include <unistd.h>
int main() { return !!syscall(__NR_close_range, 3, ~0U, 0); }
END
$ gcc -Wall -W -O2 ~/test-close_range.c
olly@gemse:~$ ./a.out ; echo $?
0
olly@gemse:~$ valgrind ./a.out ; echo $?
==539319== Memcheck, a memory error detector
==539319== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==539319== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==539319== Command: ./a.out
==539319==
--539319-- WARNING: unhandled amd64-linux syscall: 436
--539319-- You may be able to write your own handler.
--539319-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--539319-- Nevertheless we consider this a bug. Please report
--539319-- it at http://valgrind.org/support/bug_reports.html.
==539319==
==539319== HEAP SUMMARY:
==539319== in use at exit: 0 bytes in 0 blocks
==539319== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==539319==
==539319== All heap blocks were freed -- no leaks are possible
==539319==
==539319== For lists of detected and suppressed errors, rerun with: -s
==539319== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
1
OBSERVED RESULT
"WARNING: unhandled amd64-linux syscall: 436" and exit code 1
EXPECTED RESULT
No warning and exit code 0 (as without valgrind)
SOFTWARE/OS VERSIONS
Tested on Debian unstable which has valgrind 3.16.1 (not available in the
bugzilla version list).
ADDITIONAL INFORMATION
I've checked NEWS in current valgrind git and it doesn't look like this has
been fixed since 3.16.1. I also couldn't find an existing report in bugzilla.
--
You are receiving this mail because:
You are watching all bug changes.
