--- README_MISSING_SYSCALL_OR_IOCTL.orig	Thu May 23 17:27:24 2002
+++ README_MISSING_SYSCALL_OR_IOCTL	Thu May 23 17:27:45 2002
@@ -49,7 +49,7 @@
    case __NR_read: /* syscall 3 */
       /* size_t read(int fd, void *buf, size_t count); */
       must_be_writable( "read(buf)", arg2, arg3 );
-      KERNEL_DO_SYSCALL(res);
+      KERNEL_DO_SYSCALL(tid,res);
       if (!VG_(is_kerror)(res) && res > 0) {
          make_readable( arg2, res );
       }
@@ -59,7 +59,7 @@
 have the result written to, really is addressible ("writable", here).
 Hence:
 
-      must_be_writable( "read(buf)", arg2, arg3 );
+      must_be_writable( tst, "read(buf)", arg2, arg3 );
 
 which causes Valgrind to issue a warning if the address range 
 [arg2 .. arg2 + arg3 - 1] is not writable.  This is one of those
@@ -71,7 +71,7 @@
 Now Valgrind asks the kernel to do the system call, depositing the
 return code in "res":
 
-      KERNEL_DO_SYSCALL(res);
+      KERNEL_DO_SYSCALL(tid,res);
 
 Finally, the really important bit.  If, and only if, the system call
 was successful, mark the buffer as readable (ie, as having valid