Menu
▾
▴
[Valgrind-testresults] 2015-03-21 02:07:02 CET nightly build (wildebeest32, Debian 7.8 wheezy i686)
|
From: Mark W. <ma...@bu...> - 2015-03-21 03:36:18
|
valgrind revision: 15027
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-686-pae i686
Vendor version: Debian GNU/Linux 7 (wheezy)
Nightly build on wildebeest32 ( Debian 7.8 wheezy i686 )
Started at 2015-03-21 02:07:02 CET
Ended at 2015-03-21 04:32:09 CET
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
== 633 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
=================================================
== 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
== 633 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
helgrind/tests/pth_destroy_cond (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2015-03-21 03:22:35.899703002 +0100
--- new.short 2015-03-21 04:32:09.847703002 +0100
***************
*** 8,11 ****
! == 633 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! helgrind/tests/pth_destroy_cond (stderr)
--- 8,11 ----
! == 633 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
! gdbserver_tests/hgtls (stdoutB)
=================================================
./valgrind-new/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2015-03-21 03:22:50.383703002 +0100
+++ hgtls.stdoutB.out 2015-03-21 03:43:11.519703002 +0100
@@ -16,44 +16,9 @@
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test local tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test global tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test global tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test static_extern tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test static_extern tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_local tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_local tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_global tls_ip 0x........ ip 0x........ equal 1
-[New Thread ....]
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_global tls_ip 0x........ ip 0x........ equal 1
-Program exited normally.
+Program received signal SIGTRAP, Trace/breakpoint trap.
+0x........ in syscall ...
+A debugging session is active.
+ Inferior 1 [Remote target] will be detached.
+Quit anyway? (y or n) [answered Y; input not from terminal]
+Ending remote debugging.
=================================================
./valgrind-old/helgrind/tests/pth_destroy_cond.stderr.diff
=================================================
--- pth_destroy_cond.stderr.exp 2015-03-21 02:07:35.691703001 +0100
+++ pth_destroy_cond.stderr.out 2015-03-21 03:03:51.863703001 +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
|
