Summary: | unhandled syscall: 332 (inotify_init1) | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Pace Willisson <pace> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dodji, ezrareeves, jakub, njn, plepper78, radudumi, revel, tom |
Priority: | NOR | ||
Version: | 3.4.1 | ||
Target Milestone: | wanted3.5.1 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Wrap inotify_init1 syscall
valgrind-3.5.0-inotify-init1-ppc.patch valgrind-3.5.0-inotify-init1.patch |
Description
Pace Willisson
2009-08-02 17:03:00 UTC
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. *** |