|
From: Mark W. <ma...@bu...> - 2015-03-07 02:11:13
|
valgrind revision: 14983
VEX revision: 3098
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-07 02:07:02 CET
Ended at 2015-03-07 03:10:39 CET
Results unchanged 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, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
none/tests/linux/stack-overflow (stderr)
helgrind/tests/locked_vs_unlocked2 (stderr)
=================================================
./valgrind-new/helgrind/tests/locked_vs_unlocked2.stderr.diff
=================================================
--- locked_vs_unlocked2.stderr.exp 2015-03-07 02:35:11.311703001 +0100
+++ locked_vs_unlocked2.stderr.out 2015-03-07 03:00:15.271703049 +0100
@@ -16,13 +16,13 @@
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (locked_vs_unlocked2.c:59)
- Address 0x........ is 0 bytes inside data symbol "mx2b"
+ by 0x........: main (locked_vs_unlocked2.c:58)
+ Address 0x........ is 0 bytes inside data symbol "mx2a"
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (locked_vs_unlocked2.c:58)
- Address 0x........ is 0 bytes inside data symbol "mx2a"
+ by 0x........: main (locked_vs_unlocked2.c:59)
+ Address 0x........ is 0 bytes inside data symbol "mx2b"
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
=================================================
./valgrind-new/none/tests/linux/stack-overflow.stderr.diff
=================================================
--- stack-overflow.stderr.exp 2015-03-07 02:35:25.835703001 +0100
+++ stack-overflow.stderr.out 2015-03-07 02:57:32.603703001 +0100
@@ -4,7 +4,7 @@
Process terminating with default action of signal 11 (SIGSEGV)
Access not within mapped region at address 0x........
Stack overflow in thread #1: can't grow stack to 0x........
- at 0x........: main (stack-overflow.c:6)
+ at 0x........: main (stack-overflow.c:8)
If you believe this happened as a result of a stack
overflow in your program's main thread (unlikely but
possible), you can try to increase the size of the
=================================================
./valgrind-old/helgrind/tests/locked_vs_unlocked2.stderr.diff
=================================================
--- locked_vs_unlocked2.stderr.exp 2015-03-07 02:07:28.619703001 +0100
+++ locked_vs_unlocked2.stderr.out 2015-03-07 02:24:30.595701671 +0100
@@ -16,13 +16,13 @@
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (locked_vs_unlocked2.c:59)
- Address 0x........ is 0 bytes inside data symbol "mx2b"
+ by 0x........: main (locked_vs_unlocked2.c:58)
+ Address 0x........ is 0 bytes inside data symbol "mx2a"
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (locked_vs_unlocked2.c:58)
- Address 0x........ is 0 bytes inside data symbol "mx2a"
+ by 0x........: main (locked_vs_unlocked2.c:59)
+ Address 0x........ is 0 bytes inside data symbol "mx2b"
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
=================================================
./valgrind-old/none/tests/linux/stack-overflow.stderr.diff
=================================================
--- stack-overflow.stderr.exp 2015-03-07 02:07:36.399703002 +0100
+++ stack-overflow.stderr.out 2015-03-07 02:21:30.543703002 +0100
@@ -4,7 +4,7 @@
Process terminating with default action of signal 11 (SIGSEGV)
Access not within mapped region at address 0x........
Stack overflow in thread #1: can't grow stack to 0x........
- at 0x........: main (stack-overflow.c:6)
+ at 0x........: main (stack-overflow.c:8)
If you believe this happened as a result of a stack
overflow in your program's main thread (unlikely but
possible), you can try to increase the size of the
|