[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fwd: Valgrind porting
From: |
Samuel Thibault |
Subject: |
Re: Fwd: Valgrind porting |
Date: |
Sat, 11 Jan 2014 01:02:08 +0100 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
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 news is that the mach_msg syscall is quite complex.
> And then making the successful cross-compile to make it work?
Yes.
> 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?)
Kernel traps are the gnumach name for system calls.
> 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)
include/mach/syscall_sw.h
Samuel
Re: Valgrind porting, Richard Braun, 2014/01/06