From: Julian Seward Date: Thu, 7 Jul 2005 13:52:03 +0000 (+0000) Subject: Comment-only-change: record subtle interactions between self-checks X-Git-Tag: svn/VALGRIND_3_0_1^2~68 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=253f2f82d3c31be2adbb0979e123527d5310d907;p=thirdparty%2Fvalgrind.git Comment-only-change: record subtle interactions between self-checks and bb chasing. git-svn-id: svn://svn.valgrind.org/vex/trunk@1266 --- diff --git a/VEX/pub/libvex.h b/VEX/pub/libvex.h index 3e07fafb96..3935a16b70 100644 --- a/VEX/pub/libvex.h +++ b/VEX/pub/libvex.h @@ -294,6 +294,18 @@ VexTranslateResult LibVEX_Translate ( Int traceflags ); +/* 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. + + 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 ---*/