|
From: <ma...@bu...> - 2015-02-21 01:47:34
|
valgrind revision: 14950
VEX revision: 3091
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+deb7u7) 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-02-21 00:00:01 UTC
Ended at 2015-02-21 01:43:12 UTC
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... done
Regression test results follow
== 687 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
=================================================
== 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
== 687 tests, 7 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
helgrind/tests/locked_vs_unlocked2 (stderr)
drd/tests/annotate_hb_race (stderr)
drd/tests/custom_alloc (stderr)
drd/tests/custom_alloc_fiw (stderr)
drd/tests/sigalrm (stderr)
drd/tests/std_atomic (stderr)
drd/tests/str_tester (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2015-02-21 00:32:51.503768633 +0000
--- new.short 2015-02-21 01:43:12.079179973 +0000
***************
*** 4,6 ****
Building valgrind ... done
! Running regression tests ... failed
--- 4,6 ----
Building valgrind ... done
! Running regression tests ... done
***************
*** 8,17 ****
! == 687 tests, 7 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! helgrind/tests/locked_vs_unlocked2 (stderr)
! drd/tests/annotate_hb_race (stderr)
! drd/tests/custom_alloc (stderr)
! drd/tests/custom_alloc_fiw (stderr)
! drd/tests/sigalrm (stderr)
! drd/tests/std_atomic (stderr)
! drd/tests/str_tester (stderr)
--- 8,10 ----
! == 687 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
=================================================
./valgrind-old/drd/tests/annotate_hb_race.stderr.diff
=================================================
--- annotate_hb_race.stderr.exp 2015-02-21 00:01:27.408380722 +0000
+++ annotate_hb_race.stderr.out 2015-02-21 00:24:31.643914024 +0000
@@ -1,8 +1,26 @@
-Conflicting store by thread x at 0x........ size 4
- at 0x........: main (annotate_hb_race.c:?)
-Allocation context: BSS section of annotate_hb_race
-Done.
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread x: status = VgTs_Init
+ at 0x........: ???
+
+
+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: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/custom_alloc_fiw.stderr.diff
=================================================
--- custom_alloc_fiw.stderr.exp 2015-02-21 00:01:27.384380729 +0000
+++ custom_alloc_fiw.stderr.out 2015-02-21 00:27:02.747868669 +0000
@@ -1,12 +1,26 @@
---free-is-write=yes is incompatible with custom memory allocator client requests
- at 0x........: custom_alloc (custom_alloc.c:?)
- by 0x........: main (custom_alloc.c:?)
---free-is-write=yes is incompatible with custom memory allocator client requests
- at 0x........: custom_alloc (custom_alloc.c:?)
- by 0x........: make_leak (custom_alloc.c:?)
- by 0x........: main (custom_alloc.c:?)
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread 1: status = VgTs_Init
+ at 0x........: ???
+
+
+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: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/custom_alloc.stderr.diff
=================================================
--- custom_alloc.stderr.exp 2015-02-21 00:01:27.424380717 +0000
+++ custom_alloc.stderr.out 2015-02-21 00:27:02.431868763 +0000
@@ -1,3 +1,26 @@
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread 1: status = VgTs_Init
+ at 0x........: ???
+
+
+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.
+
=================================================
./valgrind-old/drd/tests/sigalrm.stderr.diff
=================================================
--- sigalrm.stderr.exp 2015-02-21 00:01:27.356380738 +0000
+++ sigalrm.stderr.out 2015-02-21 00:30:21.295810946 +0000
@@ -1,3 +1,26 @@
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread 1: status = VgTs_Init
+ at 0x........: ???
+
+
+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.
+
=================================================
./valgrind-old/drd/tests/std_atomic.stderr.diff
=================================================
--- std_atomic.stderr.exp 2015-02-21 00:01:27.356380738 +0000
+++ std_atomic.stderr.out 2015-02-21 00:30:22.879810493 +0000
@@ -1,5 +1,26 @@
-Started.
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread 1: status = VgTs_Init
+ at 0x........: ???
+
+
+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.
+
=================================================
./valgrind-old/drd/tests/str_tester.stderr.diff
=================================================
--- str_tester.stderr.exp 2015-02-21 00:01:27.384380729 +0000
+++ str_tester.stderr.out 2015-02-21 00:30:55.075801331 +0000
@@ -1,3 +1,26 @@
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_main.c:2302 (valgrind_main): Assertion 'seg' failed.
+
+host stacktrace:
+ at 0x........: show_sched_status_wrk (m_libcassert.c:?)
+
+sched status:
+ running_tid=1
+
+Thread 1: status = VgTs_Init
+ at 0x........: ???
+
+
+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.
+
=================================================
./valgrind-old/helgrind/tests/locked_vs_unlocked2.stderr.diff
=================================================
--- locked_vs_unlocked2.stderr.exp 2015-02-21 00:01:06.448387225 +0000
+++ locked_vs_unlocked2.stderr.out 2015-02-21 00:22:38.239948902 +0000
@@ -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:...)
|