================================================= ./valgrind-new/helgrind/tests/pth_destroy_cond.stderr.diff ================================================= --- pth_destroy_cond.stderr.exp 2014-10-24 02:41:05.944443247 +0100 +++ pth_destroy_cond.stderr.out 2014-10-24 02:54:10.821868689 +0100 @@ -5,6 +5,34 @@ by 0x........: pthread_create@* (hg_intercepts.c:...) by 0x........: main (pth_destroy_cond.c:29) +---Thread-Announcement------------------------------------------ + +Thread #x is the program's root thread + +---------------------------------------------------------------- + + Lock at 0x........ was first observed + at 0x........: pthread_mutex_init (hg_intercepts.c:...) + by 0x........: main (pth_destroy_cond.c:25) + Address 0x........ is 0 bytes inside data symbol "mutex" + +Possible data race during read of size 1 at 0x........ by thread #x +Locks held: 1, at address 0x........ + at 0x........: my_memcmp (hg_intercepts.c:...) + by 0x........: pthread_cond_destroy_WRK (hg_intercepts.c:...) + by 0x........: pthread_cond_destroy@* (hg_intercepts.c:...) + by 0x........: ThreadFunction (pth_destroy_cond.c:18) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 4 by thread #x +Locks held: none + ... + by 0x........: pthread_cond_wait_WRK (hg_intercepts.c:...) + by 0x........: pthread_cond_wait@* (hg_intercepts.c:...) + by 0x........: main (pth_destroy_cond.c:31) + Address 0x........ is 4 bytes inside data symbol "cond" + ---------------------------------------------------------------- Thread #x: pthread_cond_destroy: destruction of condition variable being waited upon