|
From: Tom H. <to...@co...> - 2006-08-07 07:27:07
|
In message <Pin...@mu...>
Nicholas Nethercote <nj...@cs...> 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 :)
I implemented that system call for x86 and amd64 and it should be
supported in the 3.2.0 release.
If Amadeus is still seeing this problem in 3.2.0 then he should
open a ticket for it in the bug tracker.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|