|
[Valgrind-testresults] 2015-05-24 02:07:02 CEST nightly build
(wildebeest32, Debian 7.8 wheezy i686)
From: Mark W. <ma...@bu...> - 2015-05-24 01:05:48
|
valgrind revision: 15286
VEX revision: 3146
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-05-24 02:07:02 CEST
Ended at 2015-05-24 03:05:27 CEST
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
== 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
none/tests/bug234814 (stdout)
none/tests/bug234814 (stderr)
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 ... done
Regression test results follow
== 649 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-05-24 02:40:52.914165000 +0200
--- new.short 2015-05-24 03:05:27.794165000 +0200
***************
*** 4,6 ****
Building valgrind ... done
! Running regression tests ... done
--- 4,6 ----
Building valgrind ... done
! Running regression tests ... failed
***************
*** 8,10 ****
! == 649 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
--- 8,13 ----
! == 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! none/tests/bug234814 (stdout)
! none/tests/bug234814 (stderr)
! helgrind/tests/pth_destroy_cond (stderr)
=================================================
./valgrind-new/helgrind/tests/pth_destroy_cond.stderr.diff
=================================================
--- pth_destroy_cond.stderr.exp 2015-05-24 02:41:08.610164999 +0200
+++ pth_destroy_cond.stderr.out 2015-05-24 02:56:41.110165000 +0200
@@ -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
=================================================
./valgrind-new/none/tests/bug234814.stderr.diff
=================================================
Binary files bug234814.stderr.exp and bug234814.stderr.out differ
=================================================
./valgrind-new/none/tests/bug234814.stdout.diff
=================================================
--- bug234814.stdout.exp 2015-05-24 02:41:19.638165000 +0200
+++ bug234814.stdout.out 2015-05-24 02:54:33.646165000 +0200
@@ -1,3 +0,0 @@
-I caught the SIGBUS signal!
-I caught the SIGBUS signal!
-I caught the SIGBUS signal!
|
|
From: Rhys K. <rhy...@gm...> - 2015-05-24 01:24:00
|
I'll take a look at the incremental failing test here, bug234814, that was my add. On Sunday, 24 May 2015, Mark Wielaard <ma...@bu...> wrote: > valgrind revision: 15286 > VEX revision: 3146 > 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-05-24 02:07:02 CEST > Ended at 2015-05-24 03:05:27 CEST > 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 > > == 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > none/tests/bug234814 (stdout) > none/tests/bug234814 (stderr) > 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 ... done > > Regression test results follow > > == 649 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-05-24 02:40:52.914165000 +0200 > --- new.short 2015-05-24 03:05:27.794165000 +0200 > *************** > *** 4,6 **** > Building valgrind ... done > ! Running regression tests ... done > > --- 4,6 ---- > Building valgrind ... done > ! Running regression tests ... failed > > *************** > *** 8,10 **** > > ! == 649 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, > 0 stdoutB failures, 0 post failures == > > --- 8,13 ---- > > ! == 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == > ! none/tests/bug234814 (stdout) > ! none/tests/bug234814 (stderr) > ! helgrind/tests/pth_destroy_cond (stderr) > > > > ================================================= > ./valgrind-new/helgrind/tests/pth_destroy_cond.stderr.diff > ================================================= > --- pth_destroy_cond.stderr.exp 2015-05-24 02:41:08.610164999 +0200 > +++ pth_destroy_cond.stderr.out 2015-05-24 02:56:41.110165000 +0200 > @@ -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 > ================================================= > ./valgrind-new/none/tests/bug234814.stderr.diff > ================================================= > Binary files bug234814.stderr.exp and bug234814.stderr.out differ > ================================================= > ./valgrind-new/none/tests/bug234814.stdout.diff > ================================================= > --- bug234814.stdout.exp 2015-05-24 02:41:19.638165000 +0200 > +++ bug234814.stdout.out 2015-05-24 02:54:33.646165000 +0200 > @@ -1,3 +0,0 @@ > -I caught the SIGBUS signal! > -I caught the SIGBUS signal! > -I caught the SIGBUS signal! > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > valgrind-testresults mailing list > val...@li... <javascript:;> > https://lists.sourceforge.net/lists/listinfo/valgrind-testresults > |