[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSOC - Valgrind for Hurd
From: |
Samuel Thibault |
Subject: |
Re: GSOC - Valgrind for Hurd |
Date: |
Wed, 21 May 2014 01:02:40 +0200 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Richard Braun, le Wed 21 May 2014 00:45:51 +0200, a écrit :
> On Tue, May 20, 2014 at 11:50:28PM +0200, Samuel Thibault wrote:
> > Richard Braun, le Tue 20 May 2014 23:42:24 +0200, a écrit :
> > > On Tue, May 20, 2014 at 10:50:07PM +0200, Samuel Thibault wrote:
> > > > I would advise starting with trivial system calls, such as
> > > > mach_thread_self, mach_task_self, and mach_host_self, which don't take
> > > > any parameter, and just returns a port. That'll make you implement the
> > > > basic infrastructure for the trap call.
> > >
> > > Keep in mind that, while most "system calls" are actually RPCs, a few of
> > > them actually are real system calls (i.e. traps) in addition to
> > > mach_msg. mach_thread_self and mach_task_self are such calls.
> >
> > Well, valgrind will only see system calls, not RPCs.
>
> Yes, and that's important to stress since calls like vm_map are RPCs.
There is also the system call version, actually.
Samuel