Am Mittwoch, 23. November 2005 11:57 schrieb Tom Hughes:
> In message <200511221736.47139.bartoschek@...>
> Christoph Bartoschek <bartoschek@...> wrote:
> > Am Dienstag, 22. November 2005 17:27 schrieb Tom Hughes:
> >> Ah right. Unfortunately I haven't got any 64 bit machines with 2.4
> >> kernels on them anymore.
> >> Do you actually see a call to time in the system call trace if you
> >> use --trace-syscalls=yes?
> > Yes,
> > SYSCALL[19858,1](201) sys_time ( 0x7FF000378 )[sync] -->
> > Success(0x438348BC)
> This is a bug in your kernel - in 2.4.21 the time system call is
> mapped to sys_time which treats it's argument as a pointer to an int
> and only fills in 4 bytes.
> In 2.4.32 it has been changed to use sys_time64 in the x86_64 arch
> specific code and that treats the pointer as a long point and fills
> in all 8 bytes.
> The reason you don't normally see this is that time is a vsyscall so
> is normally done in user space but valgrind deliberately disables the
> vsyscalls and forces them to be done by real system calls to the