|
[Valgrind-developers] 2010-10-18 23:26:01 CDT nightly build (ppc32,
Linux 2.6.27.45-0.1-default ppc)
From: Rich C. <rc...@wi...> - 2010-10-19 05:32:39
|
Nightly build on ppc32 ( Linux 2.6.27.45-0.1-default ppc ) Started at 2010-10-18 23:26:01 CDT Ended at 2010-10-19 00:32:22 CDT 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 == 439 tests, 86 stderr failures, 13 stdout failures, 2 post failures == memcheck/tests/badjump (stderr) memcheck/tests/badjump2 (stderr) memcheck/tests/linux/capget (stderr) memcheck/tests/linux/stack_changes (stderr) memcheck/tests/linux-syscalls-2007 (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo1 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stdout) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stdout) memcheck/tests/varinfo6 (stderr) massif/tests/deep-D (post) massif/tests/overloaded-new (post) none/tests/linux/mremap (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/power5+_round (stdout) none/tests/ppc32/power5+_round (stderr) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) none/tests/ppc32/testVMX (stdout) none/tests/ppc32/testVMX (stderr) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) helgrind/tests/hg03_inherit (stderr) helgrind/tests/hg04_race (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/rwlock_race (stderr) helgrind/tests/tc01_simple_race (stderr) helgrind/tests/tc05_simple_race (stderr) helgrind/tests/tc06_two_races (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc16_byterace (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stdout) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc23_bogus_condwait (stderr) drd/tests/annotate_barrier (stderr) drd/tests/annotate_hb_err (stderr) drd/tests/annotate_hbefore (stderr) drd/tests/annotate_ignore_read (stderr) drd/tests/annotate_ignore_rw (stderr) drd/tests/annotate_ignore_rw2 (stderr) drd/tests/annotate_ignore_write (stderr) drd/tests/annotate_ignore_write2 (stderr) drd/tests/annotate_order_1 (stderr) drd/tests/annotate_order_2 (stderr) drd/tests/annotate_order_3 (stderr) drd/tests/annotate_publish_hg (stderr) drd/tests/annotate_rwlock (stderr) drd/tests/annotate_rwlock_hg (stderr) drd/tests/annotate_smart_pointer (stderr) drd/tests/annotate_spinlock (stderr) drd/tests/annotate_static (stderr) drd/tests/annotate_trace_memory (stderr) drd/tests/atomic_var (stderr) drd/tests/boost_thread (stderr) drd/tests/bug-235681 (stderr) drd/tests/fp_race (stderr) drd/tests/hg03_inherit (stderr) drd/tests/hg04_race (stderr) drd/tests/hg05_race2 (stderr) drd/tests/linuxthreads_det (stderr) drd/tests/pth_cancel_locked (stderr) drd/tests/pth_cleanup_handler (stderr) drd/tests/pth_detached2 (stdout) drd/tests/pth_detached2 (stderr) drd/tests/pth_mutex_reinit (stderr) drd/tests/pth_once (stderr) drd/tests/pth_process_shared_mutex (stderr) drd/tests/pth_spinlock (stderr) drd/tests/pth_uninitialized_cond (stderr) drd/tests/read_after_free (stderr) drd/tests/recursive_mutex (stderr) drd/tests/rwlock_race (stderr) drd/tests/rwlock_test (stderr) drd/tests/rwlock_type_checking (stderr) drd/tests/sem_as_mutex (stderr) drd/tests/sem_as_mutex2 (stderr) drd/tests/sem_as_mutex3 (stderr) drd/tests/sem_open (stderr) drd/tests/sem_open2 (stderr) drd/tests/sem_open3 (stderr) drd/tests/sem_open_traced (stderr) drd/tests/tc01_simple_race (stderr) drd/tests/tc16_byterace (stderr) drd/tests/tc19_shadowmem (stderr) drd/tests/tc23_bogus_condwait (stderr) drd/tests/tc24_nonzero_sem (stderr) drd/tests/thread_name (stderr) ================================================= == 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 == 443 tests, 18 stderr failures, 6 stdout failures, 2 post failures == memcheck/tests/badjump (stderr) memcheck/tests/badjump2 (stderr) memcheck/tests/linux/capget (stderr) memcheck/tests/linux/stack_changes (stderr) memcheck/tests/linux-syscalls-2007 (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo6 (stderr) massif/tests/deep-D (post) massif/tests/overloaded-new (post) none/tests/linux/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/power5+_round (stdout) none/tests/ppc32/power5+_round (stderr) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) none/tests/ppc32/testVMX (stdout) none/tests/ppc32/testVMX (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc23_bogus_condwait (stderr) drd/tests/tc23_bogus_condwait (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Oct 19 00:03:09 2010 --- new.short Tue Oct 19 00:32:22 2010 *************** *** 8,10 **** ! == 443 tests, 18 stderr failures, 6 stdout failures, 2 post failures == memcheck/tests/badjump (stderr) --- 8,10 ---- ! == 439 tests, 86 stderr failures, 13 stdout failures, 2 post failures == memcheck/tests/badjump (stderr) *************** *** 16,17 **** --- 16,24 ---- memcheck/tests/supp_unknown (stderr) + memcheck/tests/varinfo1 (stderr) + memcheck/tests/varinfo2 (stderr) + memcheck/tests/varinfo3 (stderr) + memcheck/tests/varinfo4 (stdout) + memcheck/tests/varinfo4 (stderr) + memcheck/tests/varinfo5 (stderr) + memcheck/tests/varinfo6 (stdout) memcheck/tests/varinfo6 (stderr) *************** *** 20,21 **** --- 27,30 ---- none/tests/linux/mremap (stderr) + none/tests/map_unmap (stdout) + none/tests/map_unmap (stderr) none/tests/ppc32/jm-fp (stdout) *************** *** 31,36 **** --- 40,111 ---- none/tests/ppc32/testVMX (stderr) + none/tests/sigstackgrowth (stdout) + none/tests/sigstackgrowth (stderr) + none/tests/stackgrowth (stdout) + none/tests/stackgrowth (stderr) + helgrind/tests/hg03_inherit (stderr) + helgrind/tests/hg04_race (stderr) helgrind/tests/hg05_race2 (stderr) + helgrind/tests/rwlock_race (stderr) + helgrind/tests/tc01_simple_race (stderr) + helgrind/tests/tc05_simple_race (stderr) + helgrind/tests/tc06_two_races (stderr) helgrind/tests/tc06_two_races_xml (stderr) + helgrind/tests/tc16_byterace (stderr) + helgrind/tests/tc20_verifywrap (stderr) + helgrind/tests/tc21_pthonce (stdout) + helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc23_bogus_condwait (stderr) + drd/tests/annotate_barrier (stderr) + drd/tests/annotate_hb_err (stderr) + drd/tests/annotate_hbefore (stderr) + drd/tests/annotate_ignore_read (stderr) + drd/tests/annotate_ignore_rw (stderr) + drd/tests/annotate_ignore_rw2 (stderr) + drd/tests/annotate_ignore_write (stderr) + drd/tests/annotate_ignore_write2 (stderr) + drd/tests/annotate_order_1 (stderr) + drd/tests/annotate_order_2 (stderr) + drd/tests/annotate_order_3 (stderr) + drd/tests/annotate_publish_hg (stderr) + drd/tests/annotate_rwlock (stderr) + drd/tests/annotate_rwlock_hg (stderr) + drd/tests/annotate_smart_pointer (stderr) + drd/tests/annotate_spinlock (stderr) + drd/tests/annotate_static (stderr) + drd/tests/annotate_trace_memory (stderr) + drd/tests/atomic_var (stderr) + drd/tests/boost_thread (stderr) + drd/tests/bug-235681 (stderr) + drd/tests/fp_race (stderr) + drd/tests/hg03_inherit (stderr) + drd/tests/hg04_race (stderr) + drd/tests/hg05_race2 (stderr) + drd/tests/linuxthreads_det (stderr) + drd/tests/pth_cancel_locked (stderr) + drd/tests/pth_cleanup_handler (stderr) + drd/tests/pth_detached2 (stdout) + drd/tests/pth_detached2 (stderr) + drd/tests/pth_mutex_reinit (stderr) + drd/tests/pth_once (stderr) + drd/tests/pth_process_shared_mutex (stderr) + drd/tests/pth_spinlock (stderr) + drd/tests/pth_uninitialized_cond (stderr) + drd/tests/read_after_free (stderr) + drd/tests/recursive_mutex (stderr) + drd/tests/rwlock_race (stderr) + drd/tests/rwlock_test (stderr) + drd/tests/rwlock_type_checking (stderr) + drd/tests/sem_as_mutex (stderr) + drd/tests/sem_as_mutex2 (stderr) + drd/tests/sem_as_mutex3 (stderr) + drd/tests/sem_open (stderr) + drd/tests/sem_open2 (stderr) + drd/tests/sem_open3 (stderr) + drd/tests/sem_open_traced (stderr) + drd/tests/tc01_simple_race (stderr) + drd/tests/tc16_byterace (stderr) + drd/tests/tc19_shadowmem (stderr) drd/tests/tc23_bogus_condwait (stderr) + drd/tests/tc24_nonzero_sem (stderr) + drd/tests/thread_name (stderr) ================================================= ./valgrind-new/drd/tests/annotate_barrier.stderr.diff ================================================= --- annotate_barrier.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_barrier.stderr.out 2010-10-19 00:30:00.000000000 -0500 @@ -1,47 +1,21 @@ -The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_init (annotate_barrier.c:?) - by 0x........: barriers_and_races (annotate_barrier.c:?) - by 0x........: main (annotate_barrier.c:?) - -Thread 2: -The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_wait (annotate_barrier.c:?) - by 0x........: threadfunc (annotate_barrier.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) - -Thread 3: -The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_wait (annotate_barrier.c:?) - by 0x........: threadfunc (annotate_barrier.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) - -The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_wait (annotate_barrier.c:?) - by 0x........: threadfunc (annotate_barrier.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) - -Thread 2: -Conflicting store by thread 2 at 0x........ size 4 - at 0x........: threadfunc (annotate_barrier.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) - by 0x........: (within libpthread-?.?.so) -Address 0x........ is at offset 0 from 0x......... Allocation context: - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: barriers_and_races (annotate_barrier.c:?) - by 0x........: main (annotate_barrier.c:?) - -The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_wait (annotate_barrier.c:?) - by 0x........: threadfunc (annotate_barrier.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) - -Thread 1: -The annotation macro ANNOTATE_BARRIER_DESTROY has not yet been implemented in <valgrind/drd.h> - at 0x........: barrier_destroy (annotate_barrier.c:?) - by 0x........: barriers_and_races (annotate_barrier.c:?) - by 0x........: main (annotate_barrier.c:?) -Done. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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: 11 errors from 7 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_hb_err.stderr.diff ================================================= --- annotate_hb_err.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_hb_err.stderr.out 2010-10-19 00:30:01.000000000 -0500 @@ -1,25 +1,21 @@ -wrong type of synchronization object - at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?) - by 0x........: main (annotate_hb_err.c:?) -mutex 0x........ was first observed at: - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (annotate_hb_err.c:?) - -wrong type of synchronization object - at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?) - by 0x........: main (annotate_hb_err.c:?) -cond 0x........ was first observed at: - at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?) - by 0x........: main (annotate_hb_err.c:?) - -wrong type of synchronization object - at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?) - by 0x........: main (annotate_hb_err.c:?) -order annotation 0x........ was first observed at: - at 0x........: U_AnnotateHappensAfter (unified_annotations.h:?) - by 0x........: main (annotate_hb_err.c:?) -Done. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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/annotate_hbefore.stderr.diff ================================================= --- annotate_hbefore.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_hbefore.stderr.out 2010-10-19 00:30:04.000000000 -0500 @@ -1,3 +1,21 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_ignore_read.stderr.diff ================================================= --- annotate_ignore_read.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_ignore_read.stderr.out 2010-10-19 00:30:05.000000000 -0500 @@ -1,6 +1,21 @@ -FLAGS [phb=1, fm=0] -test69: negative - GLOB=30 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_ignore_rw.stderr.diff ================================================= --- annotate_ignore_rw.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_ignore_rw.stderr.out 2010-10-19 00:30:06.000000000 -0500 @@ -1,9 +1,21 @@ -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside local var "s_c" -declared at annotate_ignore_rw.c:11, in frame #? of thread 1 -Finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_ignore_rw2.stderr.diff ================================================= --- annotate_ignore_rw2.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_ignore_rw2.stderr.out 2010-10-19 00:30:07.000000000 -0500 @@ -1,19 +1,21 @@ -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside local var "s_b" -declared at annotate_ignore_rw.c:10, in frame #? of thread 1 - -Conflicting store by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside local var "s_a" -declared at annotate_ignore_rw.c:9, in frame #? of thread 1 - -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside local var "s_c" -declared at annotate_ignore_rw.c:11, in frame #? of thread 1 -Finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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/annotate_ignore_write.stderr.diff ================================================= --- annotate_ignore_write.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_ignore_write.stderr.out 2010-10-19 00:30:08.000000000 -0500 @@ -1,19 +1,21 @@ -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_b" -declared at annotate_ignore_write.c:10, in frame #? of thread 1 - -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_c" -declared at annotate_ignore_write.c:11, in frame #? of thread 1 - -Conflicting store by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_a" -declared at annotate_ignore_write.c:9, in frame #? of thread 1 -Finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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/annotate_ignore_write2.stderr.diff ================================================= --- annotate_ignore_write2.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_ignore_write2.stderr.out 2010-10-19 00:30:09.000000000 -0500 @@ -1,24 +1,21 @@ -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_b" -declared at annotate_ignore_write.c:10, in frame #? of thread 1 - -Conflicting store by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_a" -declared at annotate_ignore_write.c:9, in frame #? of thread 1 - -Conflicting load by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_c" -declared at annotate_ignore_write.c:11, in frame #? of thread 1 - -Conflicting store by thread 1 at 0x........ size 4 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside local var "s_a" -declared at annotate_ignore_write.c:9, in frame #? of thread 1 -Finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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: 4 errors from 4 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_order_1.stderr.diff ================================================= --- annotate_order_1.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_order_1.stderr.out 2010-10-19 00:30:09.000000000 -0500 @@ -1,6 +1,21 @@ -FLAGS [phb=1, fm=0] -test03: negative - GLOB=2 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_order_2.stderr.diff ================================================= --- annotate_order_2.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_order_2.stderr.out 2010-10-19 00:30:10.000000000 -0500 @@ -1,6 +1,21 @@ -FLAGS [phb=1, fm=0] -test30: negative - GLOB=47 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_order_3.stderr.diff ================================================= --- annotate_order_3.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_order_3.stderr.out 2010-10-19 00:30:11.000000000 -0500 @@ -1,6 +1,21 @@ -FLAGS [phb=1, fm=0] -test31: negative - GLOB=48 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_publish_hg.stderr.diff ================================================= --- annotate_publish_hg.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_publish_hg.stderr.out 2010-10-19 00:30:12.000000000 -0500 @@ -1,7 +1,21 @@ -The annotation macro ANNOTATE_PUBLISH_MEMORY_RANGE has not yet been implemented in <valgrind/helgrind.h> - at 0x........: main (annotate_publish_hg.c:?) -Done. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_rwlock.stderr.diff ================================================= --- annotate_rwlock.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_rwlock.stderr.out 2010-10-19 00:30:13.000000000 -0500 @@ -1,4 +1,21 @@ -Finished. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_rwlock_hg.stderr.diff ================================================= --- annotate_rwlock_hg.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_rwlock_hg.stderr.out 2010-10-19 00:30:14.000000000 -0500 @@ -1 +0,0 @@ -Total error count is below threshold. ================================================= ./valgrind-new/drd/tests/annotate_smart_pointer.stderr.diff ================================================= --- annotate_smart_pointer.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_smart_pointer.stderr.out 2010-10-19 00:30:14.000000000 -0500 @@ -1,4 +1,21 @@ -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_spinlock.stderr.diff ================================================= --- annotate_spinlock.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_spinlock.stderr.out 2010-10-19 00:30:15.000000000 -0500 @@ -1,6 +1,21 @@ -FLAGS [phb=1, fm=0] -test27: negative - GLOB=4 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_static.stderr.diff ================================================= --- annotate_static.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_static.stderr.out 2010-10-19 00:30:16.000000000 -0500 @@ -1,4 +1,21 @@ -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/annotate_trace_memory.stderr.diff ================================================= --- annotate_trace_memory.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ annotate_trace_memory.stderr.out 2010-10-19 00:30:17.000000000 -0500 @@ -1,20 +1,21 @@ -FLAGS [phb=1, fm=0] -test01: positive -store 0x........ size 4 (thread x / vc ...) - at 0x........: test01::Worker() (tsan_unittest.cpp:?) - by 0x........: MyThread::ThreadBody(MyThread*) (tsan_thread_wrappers_pthread.h:?) -store 0x........ size 4 (thread x / vc ...) - at 0x........: test01::Parent() (tsan_unittest.cpp:?) - by 0x........: test01::Run() (tsan_unittest.cpp:?) -Conflicting store by thread x at 0x........ size 4 - at 0x........: test01::Parent() (tsan_unittest.cpp:?) - by 0x........: test01::Run() (tsan_unittest.cpp:?) -Allocation context: BSS section of tsan_unittest - -load 0x........ size 4 (thread x / vc ...) - at 0x........: test01::Run() (tsan_unittest.cpp:?) - by 0x........: main (tsan_unittest.cpp:?) - GLOB=2 -ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/atomic_var.stderr.diff ================================================= --- atomic_var.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ atomic_var.stderr.out 2010-10-19 00:30:18.000000000 -0500 @@ -1,12 +1,21 @@ -Start of test. -Conflicting load by thread x at 0x........ size 4 - at 0x........: thread_func_2 (atomic_var.c:?) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside local var "s_y" -declared at atomic_var.c:35, in frame #? of thread x -y = 1 -Test finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/boost_thread.stderr.diff ================================================= --- boost_thread.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ boost_thread.stderr.out 2010-10-19 00:30:24.000000000 -0500 @@ -1,6 +1,21 @@ -Thread 1. -Thread 2. -Finished. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (in /root/src/vg/nightly/valgrind-new/drd/drd-ppc32-linux) + +sched status: + running_tid=0 + + +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-new/drd/tests/bug-235681.stderr.diff ================================================= --- bug-235681.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ bug-235681.stderr.out 2010-10-19 00:30:25.000000000 -0500 @@ -1,4 +1,21 @@ -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/fp_race.stderr.diff ================================================= --- fp_race.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ fp_race.stderr.out 2010-10-19 00:30:29.000000000 -0500 @@ -1,21 +1,21 @@ -Conflicting load by thread 1 at 0x........ size 8 - at 0x........: main (fp_race.c:?) -Location 0x........ is 0 bytes inside local var "s_d3" -declared at fp_race.c:24, in frame #? of thread 1 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) - -Conflicting store by thread 1 at 0x........ size 8 - at 0x........: main (fp_race.c:?) -Location 0x........ is 0 bytes inside local var "s_d3" -declared at fp_race.c:24, in frame #? of thread 1 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/hg03_inherit.stderr.diff ================================================= --- hg03_inherit.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ hg03_inherit.stderr.out 2010-10-19 00:30:35.000000000 -0500 @@ -1,16 +1,21 @@ -Thread 3: -Conflicting store by thread 3 at 0x........ size 4 - at 0x........: t2 (hg03_inherit.c:28) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside shared[1], -declared at hg03_inherit.c:11, in frame #? of thread 3 - -Conflicting store by thread 3 at 0x........ size 4 - at 0x........: t2 (hg03_inherit.c:29) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside shared[1], -declared at hg03_inherit.c:11, in frame #? of thread 3 +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/hg04_race.stderr.diff ================================================= --- hg04_race.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ hg04_race.stderr.out 2010-10-19 00:30:36.000000000 -0500 @@ -1,24 +1,21 @@ -Thread 3: -Conflicting load by thread 3 at 0x........ size 4 - at 0x........: th (hg04_race.c:10) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside local var "shared" -declared at hg04_race.c:6, in frame #? of thread 2 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) - -Conflicting store by thread 3 at 0x........ size 4 - at 0x........: th (hg04_race.c:10) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside local var "shared" -declared at hg04_race.c:6, in frame #? of thread 2 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/hg05_race2.stderr.diff ================================================= --- hg05_race2.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ hg05_race2.stderr.out 2010-10-19 00:30:37.000000000 -0500 @@ -1,24 +1,21 @@ -Thread 3: -Conflicting load by thread 3 at 0x........ size 4 - at 0x........: th (hg05_race2.c:17) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside foo.poot[5].plop[11], -declared at hg05_race2.c:24, in frame #? of thread 1 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) - -Conflicting store by thread 3 at 0x........ size 4 - at 0x........: th (hg05_race2.c:17) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Location 0x........ is 0 bytes inside foo.poot[5].plop[11], -declared at hg05_race2.c:24, in frame #? of thread 1 -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/hg05_race2.stderr.diff-powerpc ================================================= --- hg05_race2.stderr.exp-powerpc 2010-10-19 00:03:35.000000000 -0500 +++ hg05_race2.stderr.out 2010-10-19 00:30:37.000000000 -0500 @@ -1,22 +1,21 @@ -Thread 3: -Conflicting load by thread 3 at 0x........ size 4 - at 0x........: th (hg05_race2.c:17) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Allocation context: unknown. -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) - -Conflicting store by thread 3 at 0x........ size 4 - at 0x........: th (hg05_race2.c:17) - by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?) -Allocation context: unknown. -Other segment start (thread 2) - (thread finished, call stack no longer available) -Other segment end (thread 2) - (thread finished, call stack no longer available) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/linuxthreads_det.stderr.diff ================================================= --- linuxthreads_det.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ linuxthreads_det.stderr.out 2010-10-19 00:30:47.000000000 -0500 @@ -1,3 +1,21 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/linuxthreads_det.stderr.diff-linuxthreads ================================================= --- linuxthreads_det.stderr.exp-linuxthreads 2010-10-19 00:03:35.000000000 -0500 +++ linuxthreads_det.stderr.out 2010-10-19 00:30:47.000000000 -0500 @@ -1,7 +1,21 @@ -Detected the LinuxThreads threading library. Sorry, but DRD only supports -the newer NPTL (Native POSIX Threads Library). Please try to rerun DRD -after having upgraded to a newer version of your Linux distribution. -Giving up. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_cancel_locked.stderr.diff ================================================= --- pth_cancel_locked.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_cancel_locked.stderr.out 2010-10-19 00:31:16.000000000 -0500 @@ -1,11 +1,21 @@ -Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2. - at 0x........: pthread_join (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) -mutex 0x........ was first observed at: - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) -Test finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_cancel_locked.stderr.diff-darwin ================================================= --- pth_cancel_locked.stderr.exp-darwin 2010-10-19 00:03:35.000000000 -0500 +++ pth_cancel_locked.stderr.out 2010-10-19 00:31:16.000000000 -0500 @@ -1,18 +1,21 @@ -Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2. - at 0x........: pthread_join (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) -mutex 0x........ was first observed at: - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) - -Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2. - at 0x........: pthread_join (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) -mutex 0x........ was first observed at: - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (pth_cancel_locked.c:?) -Test finished. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_cleanup_handler.stderr.diff ================================================= --- pth_cleanup_handler.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_cleanup_handler.stderr.out 2010-10-19 00:31:17.000000000 -0500 @@ -1,6 +1,21 @@ -Cleanup handler has been called. -Cleanup handler has been called. -Test succeeded. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_detached2.stderr.diff ================================================= --- pth_detached2.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_detached2.stderr.out 2010-10-19 00:31:24.000000000 -0500 @@ -1,3 +1,21 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_detached2.stdout.diff ================================================= --- pth_detached2.stdout.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_detached2.stdout.out 2010-10-19 00:31:23.000000000 -0500 @@ -1 +0,0 @@ -.................... ================================================= ./valgrind-new/drd/tests/pth_mutex_reinit.stderr.diff ================================================= --- pth_mutex_reinit.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_mutex_reinit.stderr.out 2010-10-19 00:31:28.000000000 -0500 @@ -1,11 +1,21 @@ -Mutex reinitialization: mutex 0x........, recursion count 0, owner 1. - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (pth_mutex_reinit.c:?) -mutex 0x........ was first observed at: - at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?) - by 0x........: main (pth_mutex_reinit.c:?) -Done. +valgrind: m_mallocfree.c:1237 (unlinkBlock): Assertion 'get_next_b(b) == b' failed. + at 0x........: ??? (m_libcassert.c:?) + +sched status: + running_tid=0 + + +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-new/drd/tests/pth_once.stderr.diff ================================================= --- pth_once.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_once.stderr.out 2010-10-19 00:31:28.000000000 -0500 @@ -1 +0,0 @@ -ERROR SUMMARY: 0 errors from 0 contexts ================================================= ./valgrind-new/drd/tests/pth_process_shared_mutex.stderr.diff ================================================= --- pth_process_shared_mutex.stderr.exp 2010-10-19 00:03:35.000000000 -0500 +++ pth_process_shared_mutex.stderr.out 2010-10-19 00:31:29.000000000 -050... [truncated message content] |