Bug 232793 - unhandled syscall: 332
Summary: unhandled syscall: 332
Status: RESOLVED DUPLICATE of bug 202315
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.5.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-31 05:11 UTC by Paul Epperson
Modified: 2010-03-31 09:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Epperson 2010-03-31 05:11:35 UTC 
I invoked valgrind using:

$ valgrind nautilus

and received this in the output:

--17196-- WARNING: unhandled syscall: 332
--17196-- You may be able to write your own handler.
--17196-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--17196-- Nevertheless we consider this a bug.  Please report
--17196-- it at http://valgrind.org/support/bug_reports.html.

I attempted to follow the steps at http://valgrind.org/docs/manual/dist.readme-missing.html, but step #1 did not give me anything to go on:

$ grep 332 /usr/include/asm/unistd.h 
$
Comment 1 Tom Hughes 2010-03-31 09:24:27 UTC 

*** This bug has been marked as a duplicate of bug 202315 ***
Comment 2 Tom Hughes 2010-03-31 09:35:15 UTC 
Oh, and I've updated README_MISSING_SYSCALL_OR_IOCTL to suggest grepping in unistd*.h as (on amd64 at least) the system call numbers are in unistd_32.h and unistd_64.h now.