Updated tc20_verifywrap to current output, and documented that an error message is...

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

diff --git a/exp-drd/TODO.txt b/exp-drd/TODO.txt
index 136eddd11dde13cd3c6ae1646c38df050a931158..e08aaa3246c231982c7e964cc12d22e27fa64168 100644 (file)
--- a/exp-drd/TODO.txt
+++ b/exp-drd/TODO.txt
@@ -31,8 +31,8 @@ Data-race detection algorithm
   a crash on AMD64. Is this an exp-drd or a VEX bug ?
 - On x86 and amd64 platforms, add support for implicit locking arising from
   the use of the LOCK instruction prefix.
-- Add test programs for freeing memory that contains a condition variable /
-  destroying a condition variable being waited upon.
+- Add test programs for destroying a condition variable / semaphore / barrier
+  being waited upon.
 - Convert the array in drd_thread.c with thread information into an OSet.
 
 
@@ -66,7 +66,5 @@ Known bugs
   -- VG_(find_seginfo)() returns NULL for BSS symbols on x86_64. Not yet in
   the KDE bug tracking system.
 - tc04_free_lock fails on AMD64 + openSUSE 10.3 (free() locked mutex).
-
-Known performance issues:
-- According to cachegrind, VG_(OSet_Next)() is taking up most CPU cycles.
-  Probably due to the bitmap implementation.
+- No error message is printed for tc20_verifywrap when a locked mutex is
+  deallocated (mutex was allocated on the stack).

diff --git a/exp-drd/tests/tc20_verifywrap.stderr.exp2 b/exp-drd/tests/tc20_verifywrap.stderr.exp2
index e4bfdeb071c87da82e5cf4d55bd4e42d6e91ac57..55060b235962e605205863448ac71fc8e22c27e0 100644 (file)
--- a/exp-drd/tests/tc20_verifywrap.stderr.exp2
+++ b/exp-drd/tests/tc20_verifywrap.stderr.exp2
@@ -84,7 +84,4 @@ FIXME: can't figure out how to verify wrap of sem_post
 ------------ dealloc of mem holding locks ------------
 
 
-Destroying locked mutex: address 0x........, recursion count 1, owner 1.
-   at 0x........: main (tc20_verifywrap.c:262)
-
 ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 0 from 0)