Subhashish Pradhan, le Sat 11 Jan 2014 03:14:25 +0530, a écrit :
> So the nature of this project involves implementing all the syscalls in the
> supposed to be coregrind/m_syswrap/syswrap-hurd.c, I presume?
Yes. The good news is that there aren't many of them, just a couple
dozen. The less good ne
Hello again!
I searched and asked around for 'teaching Valgrind syscalls', and I found
that the syscall wrapper has to be implemented inside coregrind:
precisely in coregrind/m_syswrap/syswrap-*.c.
So the nature of this project involves implementing all the syscalls in the
supposed to be coregri
On Mon, Jan 06, 2014 at 01:27:08AM +0530, Subhashish Pradhan wrote:
> Has anyone started working on porting valgrind to hurd?
>
> If not, I'd like to take up the task (and for GSOC).
>
> What would be the essential skills that would be required for this task?
>
> Shell scripting, understanding o
Hello,
Subhashish Pradhan, le Mon 06 Jan 2014 09:01:26 +0530, a écrit :
> So teaching valgrind the syscall means directing memcache tool to
> intercept the read/write operations of the syscall?
It does not mean "intercepting", but writing in the valgrind source code
what read/write operations the
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
sy
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 scr
Has anyone started working on porting valgrind to hurd?
If not, I'd like to take up the task (and for GSOC).
What would be the essential skills that would be required for this task?
Shell scripting, understanding of C, and anything else?
Regards,
Subhashish
