Goplat <[EMAIL PROTECTED]> wrote:
> case 1048576:
> /* can't be bothered to calculate larger ones */
Yep. Valgrind always failed here. I did submit several bugfixes. Didn't
receive any answer. Sorry forgot to report, but my valgrind here was
always patched;
+ case 524288:
case 1048576:
+ case 1048576*2:
+ case 1048576*4:
I also needed this on my rather old system:
diff -r -ub valgrind-2.0.0/coregrind/vg_syscalls.c valgrind-2.0.0-leo/coregrind/
--- valgrind-2.0.0/coregrind/vg_syscalls.c Mon Nov 3 20:15:04 2003
+++ valgrind-2.0.0-leo/coregrind/vg_syscalls.c Mon Dec 1 16:33:56 2003
@@ -2237,6 +2237,7 @@
the number of bytes currently in that socket's send buffer.
It writes this value as an int to the memory location
indicated by the third argument of ioctl(2). */
+#if 0
case SIOCOUTQ:
SYSCALL_TRACK( pre_mem_write, tid, "ioctl(SIOCOUTQ)", arg3,
sizeof(int));
@@ -2244,6 +2245,7 @@
if (!VG_(is_kerror)(res) && res == 0)
VG_TRACK( post_mem_write,arg3, sizeof(int));
break;
+#endif
leo
