[Valgrind-developers] valgrind: r6321 - trunk/lackey

[<sv...@va...>]

Author: njn
Date: 2006-10-19 00:46:26 +0100 (Thu, 19 Oct 2006)
New Revision: 6321

Log:
Improve comments.

Modified:
   trunk/lackey/lk_main.c


Modified: trunk/lackey/lk_main.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/lackey/lk_main.c	2006-10-18 21:50:26 UTC (rev 6320)
+++ trunk/lackey/lk_main.c	2006-10-18 23:46:26 UTC (rev 6321)
@@ -106,9 +106,15 @@
 // - It does not trace into the OS kernel, so system calls and other ker=
nel
 //   operations (eg. some scheduling and signal handling code) are ignor=
ed.
 //
-// - Valgrind replaces some code with its own, notably parts of code for
-//   scheduling operations and signal handling.  This code is not traced=
.
+// - It could model loads and stores done at the system call boundary us=
ing
+//   the pre_mem_read/post_mem_write events.  For example, if you call
+//   fstat() you know that the passed in buffer has been written.  But i=
t
+//   currently does not do this.
 //
+// - Valgrind replaces some code (not much) with its own, notably parts =
of
+//   code for scheduling operations and signal handling.  This code is n=
ot
+//   traced.
+//
 // - There is no consideration of virtual-to-physical address mapping.
 //   This may not matter for many purposes.
 //