Bug fix: DRD no longer complains that a mutex was not locked by the calling thread when unlocking a mutex after a call to pthread_cond_timedwait() that timed out.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7815 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/exp-drd/drd_pthread_intercepts.c b/exp-drd/drd_pthread_intercepts.c
index a69eada..b52d5ed 100644
--- a/exp-drd/drd_pthread_intercepts.c
+++ b/exp-drd/drd_pthread_intercepts.c
@@ -459,7 +459,7 @@
cond, mutex, mutex_type(mutex), 0, 0);
CALL_FN_W_WW(ret, fn, cond, mutex);
VALGRIND_DO_CLIENT_REQUEST(res, -1, VG_USERREQ__POST_COND_WAIT,
- cond, mutex, ret == 0, 0, 0);
+ cond, mutex, 1, 0, 0);
return ret;
}
@@ -477,7 +477,7 @@
cond, mutex, mutex_type(mutex), 0, 0);
CALL_FN_W_WWW(ret, fn, cond, mutex, abstime);
VALGRIND_DO_CLIENT_REQUEST(res, -1, VG_USERREQ__POST_COND_WAIT,
- cond, mutex, ret == 0, 0, 0);
+ cond, mutex, 1, 0, 0);
return ret;
}