|
From: <sv...@va...> - 2005-07-07 13:52:10
|
Author: sewardj
Date: 2005-07-07 14:52:03 +0100 (Thu, 07 Jul 2005)
New Revision: 1266
Log:
Comment-only-change: record subtle interactions between self-checks
and bb chasing.
Modified:
trunk/pub/libvex.h
Modified: trunk/pub/libvex.h
=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/pub/libvex.h 2005-07-07 13:12:04 UTC (rev 1265)
+++ trunk/pub/libvex.h 2005-07-07 13:52:03 UTC (rev 1266)
@@ -294,7 +294,19 @@
Int traceflags
);
=20
+/* A subtlety re interaction between self-checking translations and
+ bb-chasing. The supplied chase_into_ok function should say NO
+ (False) when presented with any address for which you might want to
+ make a self-checking translation.
=20
+ If it doesn't do that, you may end up with Vex chasing from BB #1
+ to BB #2 (fine); but if you wanted checking for #2 and not #1, that
+ would not be the result. Therefore chase_into_ok should disallow
+ following into #2. That will force the caller to eventually
+ request a new translation starting at #2, at which point Vex will
+ correctly observe the make-a-self-check flag. */
+
+
/*-------------------------------------------------------*/
/*--- Show accumulated statistics ---*/
/*-------------------------------------------------------*/
|