|
From: Nicholas N. <nj...@ca...> - 2004-11-15 16:54:04
|
Hi, In vg_syscalls.c, set_tid_address is marked as a "Special" syscall, ie. one that Valgrind implements itself, rather than getting the kernel to do it. Does anyone know why this is? Valgrind currently does nothing when it is called, which is surely wrong. I think we should remove the "Special" annotation. But I'm not certain -- anyone agree/disagree? Thanks. N |
|
From: Tom H. <th...@cy...> - 2004-11-15 17:01:17
|
In message <Pin...@he...>
Nicholas Nethercote <nj...@ca...> wrote:
> In vg_syscalls.c, set_tid_address is marked as a "Special" syscall,
> ie. one that Valgrind implements itself, rather than getting the
> kernel to do it. Does anyone know why this is? Valgrind currently
> does nothing when it is called, which is surely wrong. I think we
> should remove the "Special" annotation. But I'm not certain -- anyone
> agree/disagree?
I suspect this is deliberate given that all the user level threads
are running in the same kernel thread under valgrind so we probably
don't want to be calling the actual system call here.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|