Okay! I read the ideas page, and it says as a starter, valgrind could be taught some linux ioctls.
ioctl() is a system call for controlling certain operations of hardware of the system. So teaching valgrind the syscall means directing memcache tool to intercept the read/write operations of the syscall? Is this memcache tool the one that handles read/write primitives of valgrind? Or maybe I'm wrong? Regards, Subhashish On Mon, Jan 6, 2014 at 7:15 AM, Samuel Thibault <samuel.thiba...@gnu.org>wrote: > Subhashish Pradhan, le Mon 06 Jan 2014 01:27:08 +0530, a écrit : > > Has anyone started working on porting valgrind to hurd? > > Not that I know of. > > > If not, I'd like to take up the task (and for GSOC). > > Cool :) > > > What would be the essential skills that would be required for this task? > > > > Shell scripting, understanding of C, and anything else? > > Mostly understanding C, in particular the valgrind source code, to > understand how system calls are described in there. > > You will also have to get a very good understanding of how MIG RPCs > work. > > Samuel >
