[Valgrind-testresults] 2015-03-20 00:00:01 UTC nightly build (wildebeest, Debian 7.8 wheezy x86_64)

[<ma...@bu...>]

valgrind revision: 15023
VEX revision:      3104
C compiler:        gcc (Debian 4.7.2-5) 4.7.2
GDB:               GNU gdb (GDB) 7.4.1-debian
Assembler:         GNU assembler (GNU Binutils for Debian) 2.22
C library:         GNU C Library (Debian EGLIBC 2.13-38+deb7u8) stable release version 2.13
uname -mrs:        Linux 3.2.0-4-amd64 x86_64
Vendor version:    Debian GNU/Linux 7 (wheezy)

Nightly build on wildebeest ( Debian 7.8 wheezy x86_64 )
Started at 2015-03-20 00:00:01 UTC
Ended   at 2015-03-20 01:35:32 UTC
Results differ from 24 hours ago

   Checking out valgrind source tree  ... done
   Configuring valgrind               ... done
   Building valgrind                  ... done
   Running regression tests           ... failed

Regression test results follow

== 689 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
helgrind/tests/pth_destroy_cond          (stderr)

=================================================
== Results from 24 hours ago                   ==
=================================================

   Checking out valgrind source tree  ... done
   Configuring valgrind               ... done
   Building valgrind                  ... done
   Running regression tests           ... failed

Regression test results follow

== 689 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==


=================================================
== Difference between 24 hours ago and now     ==
=================================================

*** old.short	2015-03-20 00:39:18.933673258 +0000
--- new.short	2015-03-20 01:35:32.807539911 +0000
***************
*** 8,10 ****
  
! == 689 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
  
--- 8,11 ----
  
! == 689 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! helgrind/tests/pth_destroy_cond          (stderr)
  

  
=================================================
./valgrind-new/helgrind/tests/pth_destroy_cond.stderr.diff
=================================================
--- pth_destroy_cond.stderr.exp	2015-03-20 00:39:24.861675971 +0000
+++ pth_destroy_cond.stderr.out	2015-03-20 01:06:10.530494470 +0000
@@ -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