From: Julian Seward <jseward@acm.org>
Date: Mon, 2 May 2005 12:24:39 +0000 (+0000)
Subject: Re-enable vex bb chasing.  In fact this accidentally got reenabled in
X-Git-Tag: svn/VALGRIND_3_0_0~724
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6b7de988f2e532aa4e79bde5154b7fcfa0af5237;p=thirdparty%2Fvalgrind.git

Re-enable vex bb chasing.  In fact this accidentally got reenabled in
r3582; this commit formalises that.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3594
---

diff --git a/coregrind/vg_main.c b/coregrind/vg_main.c
index 84b0c091d9..897debf431 100644
--- a/coregrind/vg_main.c
+++ b/coregrind/vg_main.c
@@ -1583,15 +1583,6 @@ static void pre_process_cmd_line_options
 
    LibVEX_default_VexControl(& VG_(clo_vex_control));
 
-   /* For the time being, disable chasing across basic block
-      boundaries.  This fools the redirector to the extent that that
-      strlen et al do not get reliably intercepted, and hence makes
-      memcheck report some false errors.  Fixing the redirector
-      properly really entails getting rid of the circularity between
-      the two memory allocators, but that is more than I have time to
-      sort out right now. */
-   //   VG_(clo_vex_control).guest_chase_thresh = 0;
-
    /* parse the options we have (only the options we care about now) */
    for (i = 1; i < vg_argc; i++) {