|
From: Amadeus W. M. <ama...@ca...> - 2006-08-07 00:20:58
|
On Mon, 07 Aug 2006 10:04:53 +1000, Nicholas Nethercote wrote: > On Sun, 6 Aug 2006, Amadeus W. M. wrote: > >> I'm trying to debug a gtkmm program I'm writing, using valgrind. >> Each time I get the following >> >> --17079-- WARNING: unhandled syscall: 311 >> --17079-- You may be able to write your own handler. >> --17079-- Read the file README_MISSING_SYSCALL_OR_IOCTL. >> >> I followed closely the instructions in README_MISSING_SYSCALL_OR_IOCTL. >> but the system calls in /usr/include/asm/unistd.h end at 309. >> There's no system call 311. >> >> What next? And how come? > > New syscalls get added to Linux every so often. Look in Valgrind's source > code at coregrind/vki_unistd-x86-linux.h (or similar file if you're on a > different platform). If you are on x86/Linux, 311 is "set_robust_list"... > your next job is to work out what it does :) > > Nick Thanks for the quick reply. Sorry, I forgot to mention in my first post, I'm running Fedora Core 5 with kernel-smp-2.6.17-1.2157_FC5. I downloaded the valgrind source, and I did see set_robust_list in vki_unista-x86-linux.h. First of all, why does valgrind have a different list of syscalls than the system itself? Second, exactly how do I know what that system call is supposed to do? I ain't psychic. |