Reinstate use of VG_(do_sanity_checks), although at a lower frequency
than before. Turns out they were wasting 25-50% of total execution
time in valgrinds of the 200203XX vintage. Apologies, KDE hackers!
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@182 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/vg_scheduler.c b/vg_scheduler.c
index 536f721..61ae9ce 100644
--- a/vg_scheduler.c
+++ b/vg_scheduler.c
@@ -1150,6 +1150,7 @@
Be paranoid. Always a good idea. */
stage1:
scheduler_sanity();
+ VG_(do_sanity_checks)( False );
/* ======================= Phase 1 of 3 =======================
Handle I/O completions and signals. This may change the
@@ -1196,7 +1197,7 @@
POSIX standard appears to require this behaviour. */
sigs_delivered = VG_(deliver_signals)( 1 /*HACK*/ );
if (sigs_delivered)
- VG_(do_sanity_checks)( 1 /*HACK*/, False );
+ VG_(do_sanity_checks)( False );
/* Try and find a thread (tid) to run. */
tid_next = tid;