Re: Valgrind porting

[Subhashish Pradhan]

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 coregrind/m_syswrap/syswrap-hurd.c, I presume?

And then making the successful cross-compile to make it work?

This is the second step as written in the project idea page, the first being
doing the corresponding for kernel traps. (So how would these kernel traps

be implemented, is the coregrind, I presume?)

Where in the source of hurd/mach shall I find all the syscalls and kernel traps,

so that I could make a list of them to study and to work on them? (the directory)

I'll dig into the background knowledge for RPCs (syscalls) and kernel traps

this week on.

Feedbacks, please.

Regards,

Subhashish

On Mon, Jan 6, 2014 at 2:25 PM, Samuel Thibault <samuel.thibault@gnu.org> wrote:

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 syscall is supposed to be doing: valgrind
does not intercept anything, it just knows what syscalls are supposed to
read and write.

> Is this memcache tool the one that handles read/write primitives of
> valgrind?

Yes.

Samuel