|
From: Rich C. <rc...@wi...> - 2016-02-18 03:56:11
|
valgrind revision: 15794
VEX revision: 3210
C compiler: gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064]
GDB: GNU gdb (GDB; openSUSE 13.2) 7.8
Assembler: GNU assembler (GNU Binutils; openSUSE 13.2) 2.24.0.20140403-6.1
C library: GNU C Library (GNU libc) stable release version 2.19 (git 9a869d822025)
uname -mrs: Linux 3.16.7-29-desktop x86_64
Vendor version: openSUSE 13.2 (Harlequin)
Nightly build on ultra ( gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064] Linux 3.16.7-29-desktop x86_64 )
Started at 2016-02-17 21:30:01 CST
Ended at 2016-02-17 21:56:02 CST
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
== 644 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/cond_timedwait_test (stderr)
helgrind/tests/hg05_race2 (stderr)
drd/tests/pth_inconsistent_cond_wait (stderr)
Last 20 lines of verbose log follow echo
-- Finished tests in exp-sgcheck/tests ---------------------------------
-- Running tests in exp-bbv/tests/amd64-linux -------------------------
clone_test: valgrind --interval-size=100000 --bb-out-file=clone_test.out.bb --pc-out-file=clone_test.out.pc ./clone_test
complex_rep: valgrind --interval-size=100000 --bb-out-file=complex_rep.out.bb ./complex_rep
fldcw_check: valgrind --interval-size=10000 --bb-out-file=fldcw_check.out.bb ./fldcw_check
ll: valgrind --interval-size=1000 --bb-out-file=ll.out.bb ./ll
million: valgrind --interval-size=100000 --bb-out-file=million.out.bb ./million
rep_prefix: valgrind --interval-size=100000 --bb-out-file=rep_prefix.out.bb ./rep_prefix
-- Finished tests in exp-bbv/tests/amd64-linux -------------------------
== 644 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/cond_timedwait_test (stderr)
helgrind/tests/hg05_race2 (stderr)
drd/tests/pth_inconsistent_cond_wait (stderr)
...checking makefile consistency
...checking header files and include directives
Makefile:1317: recipe for target 'regtest' failed
make: *** [regtest] Error 1
=================================================
== 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
== 644 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/hg05_race2 (stderr)
Last 20 lines of verbose log follow echo
preen_invars: valgrind ./preen_invars
stackerr: valgrind --num-callers=3 ./stackerr
-- Finished tests in exp-sgcheck/tests ---------------------------------
-- Running tests in exp-bbv/tests/amd64-linux -------------------------
clone_test: valgrind --interval-size=100000 --bb-out-file=clone_test.out.bb --pc-out-file=clone_test.out.pc ./clone_test
complex_rep: valgrind --interval-size=100000 --bb-out-file=complex_rep.out.bb ./complex_rep
fldcw_check: valgrind --interval-size=10000 --bb-out-file=fldcw_check.out.bb ./fldcw_check
ll: valgrind --interval-size=1000 --bb-out-file=ll.out.bb ./ll
million: valgrind --interval-size=100000 --bb-out-file=million.out.bb ./million
rep_prefix: valgrind --interval-size=100000 --bb-out-file=rep_prefix.out.bb ./rep_prefix
-- Finished tests in exp-bbv/tests/amd64-linux -------------------------
== 644 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/hg05_race2 (stderr)
...checking makefile consistency
...checking header files and include directives
Makefile:1317: recipe for target 'regtest' failed
make: *** [regtest] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Wed Feb 17 21:43:06 2016
--- new.short Wed Feb 17 21:56:02 2016
***************
*** 8,12 ****
! == 644 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/hg05_race2 (stderr)
--- 8,14 ----
! == 644 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
+ helgrind/tests/cond_timedwait_test (stderr)
helgrind/tests/hg05_race2 (stderr)
+ drd/tests/pth_inconsistent_cond_wait (stderr)
***************
*** 14,17 ****
Last 20 lines of verbose log follow echo
- preen_invars: valgrind ./preen_invars
- stackerr: valgrind --num-callers=3 ./stackerr
-- Finished tests in exp-sgcheck/tests ---------------------------------
--- 16,17 ----
***************
*** 26,30 ****
! == 644 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
helgrind/tests/hg05_race2 (stderr)
--- 26,32 ----
! == 644 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
+ helgrind/tests/cond_timedwait_test (stderr)
helgrind/tests/hg05_race2 (stderr)
+ drd/tests/pth_inconsistent_cond_wait (stderr)
=================================================
./valgrind-new/drd/tests/pth_inconsistent_cond_wait.stderr.diff1
=================================================
--- pth_inconsistent_cond_wait.stderr.exp1 2016-02-17 21:43:17.492079632 -0600
+++ pth_inconsistent_cond_wait.stderr.out 2016-02-17 21:54:07.184264204 -0600
@@ -1,39 +1,47 @@
-Thread 3:
-Inconsistent association of condition variable and mutex: condition variable 0x........, mutexes 0x........ and 0x........
- at 0x........: pthread_cond_timedwait (drd_pthread_intercepts.c:?)
+VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
+si_code=1; Faulting address: 0x........; sp: 0x........
+
+valgrind: the 'impossible' happened:
+ Killed by fatal signal
+
+host stacktrace:
+ at 0x........: ???
+ by 0x........: vgSysWrap_linux_sys_futex_before (syswrap-linux.c:1170)
+ by 0x........: vgPlain_client_syscall (syswrap-main.c:1906)
+ by 0x........: handle_syscall (scheduler.c:?)
+ by 0x........: vgPlain_scheduler (scheduler.c:?)
+ by 0x........: thread_wrapper (syswrap-linux.c:102)
+ by 0x........: run_a_thread_NORETURN (syswrap-linux.c:155)
+ by 0x........: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:324)
+ by 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-new/drd/drd-amd64-linux)
+ by 0x........: ???
+ by 0x........: ???
+ by 0x........: ???
+
+sched status:
+ running_tid=2
+
+Thread 1: status = VgTs_Yielding (lwpid 21857)
+ at 0x........: clone (in /...libc...)
+
+Thread 2: status = VgTs_Runnable (lwpid 21859)
+ at 0x........: pthread_cond_timedwait@@GLIBC_2.3.2(within libpthread-?.?.so)
+ by 0x........: pthread_cond_timedwait (drd_pthread_intercepts.c:?)
by 0x........: thread_func (pth_inconsistent_cond_wait.c:?)
by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-
-Thread 1:
-Probably a race condition: condition variable 0x........ has been signaled but the associated mutex 0x........ is not locked by the signalling thread.
- at 0x........: pthread_cond_signal (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-
-Probably a race condition: condition variable 0x........ has been signaled but the associated mutex 0x........ is not locked by the signalling thread.
- at 0x........: pthread_cond_signal (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
+ by 0x........: (within libpthread-?.?.so)
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/pth_inconsistent_cond_wait.stderr.diff2
=================================================
--- pth_inconsistent_cond_wait.stderr.exp2 2016-02-17 21:43:17.493079605 -0600
+++ pth_inconsistent_cond_wait.stderr.out 2016-02-17 21:54:07.184264204 -0600
@@ -1,39 +1,47 @@
-Thread 2:
-Inconsistent association of condition variable and mutex: condition variable 0x........, mutexes 0x........ and 0x........
- at 0x........: pthread_cond_timedwait (drd_pthread_intercepts.c:?)
+VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
+si_code=1; Faulting address: 0x........; sp: 0x........
+
+valgrind: the 'impossible' happened:
+ Killed by fatal signal
+
+host stacktrace:
+ at 0x........: ???
+ by 0x........: vgSysWrap_linux_sys_futex_before (syswrap-linux.c:1170)
+ by 0x........: vgPlain_client_syscall (syswrap-main.c:1906)
+ by 0x........: handle_syscall (scheduler.c:?)
+ by 0x........: vgPlain_scheduler (scheduler.c:?)
+ by 0x........: thread_wrapper (syswrap-linux.c:102)
+ by 0x........: run_a_thread_NORETURN (syswrap-linux.c:155)
+ by 0x........: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:324)
+ by 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-new/drd/drd-amd64-linux)
+ by 0x........: ???
+ by 0x........: ???
+ by 0x........: ???
+
+sched status:
+ running_tid=2
+
+Thread 1: status = VgTs_Yielding (lwpid 21857)
+ at 0x........: clone (in /...libc...)
+
+Thread 2: status = VgTs_Runnable (lwpid 21859)
+ at 0x........: pthread_cond_timedwait@@GLIBC_2.3.2(within libpthread-?.?.so)
+ by 0x........: pthread_cond_timedwait (drd_pthread_intercepts.c:?)
by 0x........: thread_func (pth_inconsistent_cond_wait.c:?)
by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-
-Thread 1:
-Probably a race condition: condition variable 0x........ has been signaled but the associated mutex 0x........ is not locked by the signalling thread.
- at 0x........: pthread_cond_signal (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-
-Probably a race condition: condition variable 0x........ has been signaled but the associated mutex 0x........ is not locked by the signalling thread.
- at 0x........: pthread_cond_signal (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (pth_inconsistent_cond_wait.c:?)
+ by 0x........: (within libpthread-?.?.so)
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2016-02-17 21:43:09.752291331 -0600
+++ hgtls.stdoutB.out 2016-02-17 21:45:54.906772805 -0600
@@ -26,10 +26,10 @@
test static_extern tls_ip 0x........ ip 0x........ equal 1
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test so_local tls_ip 0x........ ip 0x........ equal 1
=================================================
./valgrind-new/helgrind/tests/cond_timedwait_test.stderr.diff
=================================================
--- cond_timedwait_test.stderr.exp 2016-02-17 21:43:13.353192840 -0600
+++ cond_timedwait_test.stderr.out 2016-02-17 21:51:23.289773604 -0600
@@ -1,3 +1,32 @@
+VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
+si_code=1; Faulting address: 0x........; sp: 0x........
+
+valgrind: the 'impossible' happened:
+ Killed by fatal signal
+
+host stacktrace:
+ ...
+
+sched status:
+ running_tid=1
+
+Thread x: status = VgTs_Runnable (lwpid 14679)
+ ...
+ by 0x........: pthread_cond_timedwait_WRK (hg_intercepts.c:...)
+ by 0x........: pthread_cond_timedwait@* (hg_intercepts.c:...)
+ by 0x........: main (cond_timedwait_test.c:13)
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/helgrind/tests/hg05_race2.stderr.diff
=================================================
--- hg05_race2.stderr.exp 2016-02-17 21:43:13.346193031 -0600
+++ hg05_race2.stderr.out 2016-02-17 21:51:33.876482366 -0600
@@ -26,8 +26,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
----------------------------------------------------------------
@@ -42,8 +41,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2016-02-17 21:30:16.994463041 -0600
+++ hgtls.stdoutB.out 2016-02-17 21:32:58.281997077 -0600
@@ -26,10 +26,10 @@
test static_extern tls_ip 0x........ ip 0x........ equal 1
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test so_local tls_ip 0x........ ip 0x........ equal 1
=================================================
./valgrind-old/helgrind/tests/hg05_race2.stderr.diff
=================================================
--- hg05_race2.stderr.exp 2016-02-17 21:30:21.535337254 -0600
+++ hg05_race2.stderr.out 2016-02-17 21:38:37.057746292 -0600
@@ -26,8 +26,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
----------------------------------------------------------------
@@ -42,8 +41,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
|