as you asked reporting: Warning: noted but unhandled ioctl 0x4c01 with no size/direction hints. (1) ==1149== This could cause spurious value errors to appear. (1) ==1149== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. (1) --1149-- WARNING: unhandled amd64-linux syscall: 167 (1) --1149-- You may be able to write your own handler. (1) --1149-- Read the file README_MISSING_SYSCALL_OR_IOCTL. (1) --1149-- Nevertheless we consider this a bug. Please report (1) --1149-- it at http://valgrind.org/support/bug_reports.html. (1) --1149-- WARNING: unhandled amd64-linux syscall: 167 (1) --1149-- You may be able to write your own handler. (1) --1149-- Read the file README_MISSING_SYSCALL_OR_IOCTL. (1) --1149-- Nevertheless we consider this a bug. Please report (1) --1149-- it at http://valgrind.org/support/bug_reports.html.
What platform (OS/architecture) is this?
amd64-linux syscall 167 is swapon for which valgrind only has an implementation for mip64, but no other arches apparently.
Hmm, we should pull those wrappers about of being mips64-linux specific bucket and make them linux-general instead. Also it looks like they are missing a PRE_MEM_RASCIIZ call on the path arguments, assuming it's a normal zero terminated C string.
s/about of being/out of the