|
From: <sv...@va...> - 2005-05-02 12:25:15
|
Author: sewardj
Date: 2005-05-02 13:24:39 +0100 (Mon, 02 May 2005)
New Revision: 3594
Modified:
trunk/coregrind/vg_main.c
Log:
Re-enable vex bb chasing. In fact this accidentally got reenabled in
r3582; this commit formalises that.
Modified: trunk/coregrind/vg_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/coregrind/vg_main.c 2005-05-02 10:39:16 UTC (rev 3593)
+++ trunk/coregrind/vg_main.c 2005-05-02 12:24:39 UTC (rev 3594)
@@ -1583,15 +1583,6 @@
=20
LibVEX_default_VexControl(& VG_(clo_vex_control));
=20
- /* 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 =3D 0;
-
/* parse the options we have (only the options we care about now) */
for (i =3D 1; i < vg_argc; i++) {
=20
|