<<<test_start>>> tag=sysfs01_valgrind_memory_leak_check stime=1474225812 cmdline=" valgrind -q --leak-check=full --trace-children=yes sysfs01" contacts="" analysis=exit <<<test_output>>> --26537-- WARNING: unhandled amd64-linux syscall: 139 --26537-- You may be able to write your own handler. --26537-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --26537-- Nevertheless we consider this a bug. Please report --26537-- it at http://valgrind.org/support/bug_reports.html. sysfs01 1 TCONF : sysfs01.c:94: syscall(139) __NR_sysfs not supported on your arch sysfs01 2 TCONF : sysfs01.c:94: Remaining cases not appropriate for configuration <<<execution_status>>> initiation_status="ok" duration=1 termination_type=exited termination_id=32 corefile=no cutime=61 cstime=1 <<<test_end>>> Reproducible: Always
Can we close it? IIRC it was merged into valgrind.
I see no sign that this has been added.
This has only been implemented for Solaris. NOTES This System-V derived system call is obsolete; don't use it. On sys‐ tems with /proc, the same information can be obtained via /proc/filesystems; use that interface instead.
As sysfs() is obsolete there is no sense in keeping this bug open.