Hello, I am using the exp-ptrcheck valgrind tool on 64 bit intel (although the tool seems to have detected amd64) and I'm hitting an unhandled syscall 284 error. I did a quick search, syscall 284 appears to be sys_waitid. Is this a known issue? How should I proceed?
Thanks Dan ==00:00:00:00.000 26383== exp-ptrcheck, a heap, stack and global array overrun detector ==00:00:00:00.000 26383== NOTE: This is an Experimental-Class Valgrind Tool ==00:00:00:00.000 26383== Copyright (C) 2003-2010, and GNU GPL'd, by OpenWorks Ltd et al. ==00:00:00:00.000 26383== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info ==00:00:00:00.000 26383== Command: /usr/local/azuki/awp/bin/AwpManager ==00:00:00:00.000 26383== Parent PID: 26357 ==00:00:00:00.000 26383== sysno == 284 exp-ptrcheck: the 'impossible' happened: unhandled syscall ==00:00:00:13.680 26383== at 0x38013727: report_and_quit (m_libcassert.c:193) ==00:00:00:13.680 26383== by 0x38013799: panic (m_libcassert.c:277) ==00:00:00:13.680 26383== by 0x380137CB: vgPlain_tool_panic (m_libcassert.c:292) ==00:00:00:13.680 26383== by 0x380038CF: h_post_syscall (h_main.c:2600) ==00:00:00:13.680 26383== by 0x38051140: vgPlain_post_syscall (syswrap-main.c:1726) ==00:00:00:13.680 26383== by 0x38051D95: vgPlain_client_syscall (syswrap-main.c:1627) ==00:00:00:13.680 26383== by 0x3804F2B1: vgPlain_scheduler (scheduler.c:895) ==00:00:00:13.680 26383== by 0x380750DE: run_a_thread_NORETURN (syswrap-linux.c:94) ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
