Version: 3.4.1 (using KDE 4.2.2) Compiler: gcc 4.3.3 OS: Linux Installed from: Ubuntu Packages valgrind does not handle the inotify_init1 system call compile the program below (no compiler flags needed), run as: $ valgrind ./a.out in the output you'll find: --8641-- WARNING: unhandled syscall: 332 --8641-- You may be able to write your own handler. --8641-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --8641-- Nevertheless we consider this a bug. Please report --8641-- it at http://valgrind.org/support/bug_reports.html. inotify_init1: Function not implemented #include <stdio.h> #include <stdlib.h> #include <sys/inotify.h> int main (int argc, char **argv) { int fd; if ((fd = inotify_init1 (0)) < 0) { perror ("inotify_init1"); exit (1); } printf ("ok\n"); return (0); }
On x86_64 systems, this syscall number is 294. The same is needed there.
Created attachment 37381 [details] Wrap inotify_init1 syscall This patch wraps the inotify_init1 syscall for linux x86_32 and amd64. Tested on amd64.
Created attachment 37536 [details] valgrind-3.5.0-inotify-init1-ppc.patch No reason to leave ppc32/ppc64 out...
Created attachment 37564 [details] valgrind-3.5.0-inotify-init1.patch Updated patch, Dodji's original patch had a typo on x86 (LINKX_ instead of LINX_). This one covers all arches.
Fixed in r10909.
On ppc32-linux the syscall isn't wired yet though.
Not sure how I missed that... Fixed in r10912.
*** Bug 230407 has been marked as a duplicate of this bug. ***
*** Bug 231076 has been marked as a duplicate of this bug. ***
*** Bug 232793 has been marked as a duplicate of this bug. ***
*** Bug 241903 has been marked as a duplicate of this bug. ***