Re: [Valgrind-developers] adding system call support

[Tom H. <th...@cy...>]

In message <Pin...@sc...>
          Bob Friesenhahn <bfr...@si...> wrote:

> On Sat, 12 Jun 2004, Tom Hughes wrote:
> 
> > Under valgrind the thread handle is not a pointer, it is a small
> > unique integer, hance the attempt to access a low address.
> >
> > In fact we are better off not implementing the timer system calls
> > for now as librt will take ENOSYS as a trigger to fall back to the
> > old way of doing things with a thread that blocks with a futex for
> > the required length of time and then runs the handler function.
> 
> Surely something must be done in valgrind.  Prior to my updates,
> valgrind simply asserted since the timer_* system calls were not
> supported.  What must be done to keep valgrind from asserting while
> allowing librt to emulate the real thing?

What was the assertion? I found that I just got a warning about
system call 266 not being implemented (that's clock_getres) and it
then fell back to the old technique that was used with 2.4 kernels
that didn't have the timer system calls.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/