[Valgrind-developers] valgrind: r6329 - branches/VALGRIND_3_2_BRANCH/lackey

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

Author: njn
Date: 2006-10-20 23:54:20 +0100 (Fri, 20 Oct 2006)
New Revision: 6329

Log:
Merge minor improvements to Lackey from the trunk.

Modified:
   branches/VALGRIND_3_2_BRANCH/lackey/lk_main.c


Modified: branches/VALGRIND_3_2_BRANCH/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
--- branches/VALGRIND_3_2_BRANCH/lackey/lk_main.c	2006-10-20 22:52:34 UTC=
 (rev 6328)
+++ branches/VALGRIND_3_2_BRANCH/lackey/lk_main.c	2006-10-20 22:54:20 UTC=
 (rev 6329)
@@ -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.
 //
@@ -811,7 +817,7 @@
    VG_(details_copyright_author)(
       "Copyright (C) 2002-2006, and GNU GPL'd, by Nicholas Nethercote.")=
;
    VG_(details_bug_reports_to)  (VG_BUGS_TO);
-   VG_(details_avg_translation_sizeB) ( 175 );
+   VG_(details_avg_translation_sizeB) ( 200 );
=20
    VG_(basic_tool_funcs)          (lk_post_clo_init,
                                    lk_instrument,