|
From: Rich C. <rc...@wi...> - 2014-06-16 02:16:07
|
valgrind revision: 14043 VEX revision: 2878 C compiler: gcc (SUSE Linux) 4.8.1 20130909 [gcc-4_8-branch revision 202388] GDB: GNU gdb (GDB; openSUSE Factory) 7.6.50.20130731-cvs Assembler: GNU assembler (GNU Binutils; openSUSE Factory) 2.23.2 C library: GNU C Library (GNU libc) stable release version 2.18 (git ) uname -mrs: Linux 3.11.4-3-desktop x86_64 Vendor version: Welcome to openSUSE 13.1 "Bottle" Beta 1 - Kernel %r (%t). Nightly build on rodan ( Linux 3.11.4-3-desktop x86_64 ) Started at 2014-06-15 19:22:01 CDT Ended at 2014-06-15 21:15:58 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 == 599 tests, 89 stderr failures, 7 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/dw4 (stderr) memcheck/tests/err_disable3 (stderr) memcheck/tests/err_disable4 (stderr) memcheck/tests/threadname (stderr) memcheck/tests/threadname_xml (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) memcheck/tests/vbit-test/vbit-test (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) drd/tests/annotate_barrier (stderr) drd/tests/annotate_barrier_xml (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_sem (stderr) drd/tests/annotate_smart_pointer (stderr) drd/tests/annotate_smart_pointer2 (stderr) drd/tests/annotate_spinlock (stderr) drd/tests/annotate_static (stderr) drd/tests/annotate_trace_memory (stderr) drd/tests/annotate_trace_memory_xml (stderr) drd/tests/atomic_var (stderr) drd/tests/boost_thread (stderr) drd/tests/bug-235681 (stderr) drd/tests/concurrent_close (stderr) drd/tests/fp_race (stderr) drd/tests/fp_race_xml (stderr) drd/tests/free_is_write (stderr) drd/tests/free_is_write2 (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 (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/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/sem_wait (stderr) drd/tests/tc01_simple_race (stderr) drd/tests/tc16_byterace (stderr) drd/tests/tc19_shadowmem (stderr) drd/tests/tc24_nonzero_sem (stderr) drd/tests/thread_name (stderr) drd/tests/thread_name_xml (stderr) exp-sgcheck/tests/bad_percentify (stdout) exp-sgcheck/tests/bad_percentify (stderr) exp-sgcheck/tests/globalerr (stderr) exp-sgcheck/tests/hackedbz2 (stdout) exp-sgcheck/tests/hackedbz2 (stderr) exp-sgcheck/tests/hsg (stdout) exp-sgcheck/tests/hsg (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) exp-sgcheck/tests/stackerr (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 == 596 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable3 (stderr) memcheck/tests/err_disable4 (stderr) memcheck/tests/threadname (stderr) memcheck/tests/threadname_xml (stderr) exp-sgcheck/tests/hackedbz2 (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Jun 15 20:31:54 2014 --- new.short Sun Jun 15 21:15:58 2014 *************** *** 8,10 **** ! == 596 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable3 (stderr) --- 8,11 ---- ! == 599 tests, 89 stderr failures, 7 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == ! memcheck/tests/dw4 (stderr) memcheck/tests/err_disable3 (stderr) *************** *** 13,15 **** --- 14,106 ---- memcheck/tests/threadname_xml (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) + memcheck/tests/vbit-test/vbit-test (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) + drd/tests/annotate_barrier (stderr) + drd/tests/annotate_barrier_xml (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_sem (stderr) + drd/tests/annotate_smart_pointer (stderr) + drd/tests/annotate_smart_pointer2 (stderr) + drd/tests/annotate_spinlock (stderr) + drd/tests/annotate_static (stderr) + drd/tests/annotate_trace_memory (stderr) + drd/tests/annotate_trace_memory_xml (stderr) + drd/tests/atomic_var (stderr) + drd/tests/boost_thread (stderr) + drd/tests/bug-235681 (stderr) + drd/tests/concurrent_close (stderr) + drd/tests/fp_race (stderr) + drd/tests/fp_race_xml (stderr) + drd/tests/free_is_write (stderr) + drd/tests/free_is_write2 (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 (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/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/sem_wait (stderr) + drd/tests/tc01_simple_race (stderr) + drd/tests/tc16_byterace (stderr) + drd/tests/tc19_shadowmem (stderr) + drd/tests/tc24_nonzero_sem (stderr) + drd/tests/thread_name (stderr) + drd/tests/thread_name_xml (stderr) + exp-sgcheck/tests/bad_percentify (stdout) + exp-sgcheck/tests/bad_percentify (stderr) + exp-sgcheck/tests/globalerr (stderr) + exp-sgcheck/tests/hackedbz2 (stdout) exp-sgcheck/tests/hackedbz2 (stderr) + exp-sgcheck/tests/hsg (stdout) + exp-sgcheck/tests/hsg (stderr) + exp-sgcheck/tests/preen_invars (stdout) + exp-sgcheck/tests/preen_invars (stderr) + exp-sgcheck/tests/stackerr (stderr) ================================================= ./valgrind-new/drd/tests/annotate_barrier.stderr.diff ================================================= --- annotate_barrier.stderr.exp 2014-06-15 20:37:07.242128281 -0500 +++ annotate_barrier.stderr.out 2014-06-15 21:12:04.278454852 -0500 @@ -1,47 +1,23 @@ -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_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -ERROR SUMMARY: 11 errors from 7 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_barrier_xml.stderr.diff ================================================= --- annotate_barrier_xml.stderr.exp 2014-06-15 20:37:07.230128142 -0500 +++ annotate_barrier_xml.stderr.out 2014-06-15 21:12:04.495457369 -0500 @@ -26,302 +26,26 @@ </argv> </args> -<status> - <state>RUNNING</state> - <time>...</time> -</status> - -<error> - <unique>0x........</unique> - <tid>...</tid> - <kind>UnimpDrdClReq</kind> - <what>The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h></what> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>barrier_init</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>barriers_and_races</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - </stack> -</error> - -<error> - <unique>0x........</unique> - <tid>...</tid> - <kind>UnimpDrdClReq</kind> - <what>The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h></what> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>barrier_wait</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>threadfunc</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>vgDrd_thread_wrapper</fn> - <dir>...</dir> - <file>drd_pthread_intercepts.c</file> - <line>...</line> - </frame> - </stack> -</error> - -<error> - <unique>0x........</unique> - <tid>...</tid> - <kind>UnimpDrdClReq</kind> - <what>The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h></what> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>barrier_wait</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>threadfunc</fn> - <dir>...</dir> - <file>annotate_barrier.c</file> - <line>...</line> - </frame> - <frame> <truncated beyond 100 lines> ================================================= ./valgrind-new/drd/tests/annotate_hb_err.stderr.diff ================================================= --- annotate_hb_err.stderr.exp 2014-06-15 20:37:07.267128571 -0500 +++ annotate_hb_err.stderr.out 2014-06-15 21:12:04.663459318 -0500 @@ -1,25 +1,23 @@ -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_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_hbefore.stderr.diff ================================================= --- annotate_hbefore.stderr.exp 2014-06-15 20:37:07.082126425 -0500 +++ annotate_hbefore.stderr.out 2014-06-15 21:12:06.763483679 -0500 @@ -1,3 +1,23 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_read.stderr.diff ================================================= --- annotate_ignore_read.stderr.exp 2014-06-15 20:37:07.220128026 -0500 +++ annotate_ignore_read.stderr.out 2014-06-15 21:12:07.125487879 -0500 @@ -1,6 +1,23 @@ -FLAGS [phb=1, fm=0] -test69: negative - GLOB=30 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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 2014-06-15 20:37:07.075126344 -0500 +++ annotate_ignore_rw.stderr.out 2014-06-15 21:12:07.294489839 -0500 @@ -1,9 +1,23 @@ -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside global var "s_c" -declared at annotate_ignore_rw.c:12 -Finished. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -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 2014-06-15 20:37:07.237128223 -0500 +++ annotate_ignore_rw2.stderr.out 2014-06-15 21:12:07.420491301 -0500 @@ -1,19 +1,23 @@ -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside global var "s_b" -declared at annotate_ignore_rw.c:11 - -Conflicting store by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside global var "s_a" -declared at annotate_ignore_rw.c:10 - -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_rw.c:?) -Location 0x........ is 0 bytes inside global var "s_c" -declared at annotate_ignore_rw.c:12 -Finished. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -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 2014-06-15 20:37:07.132127005 -0500 +++ annotate_ignore_write.stderr.out 2014-06-15 21:12:07.562492948 -0500 @@ -1,19 +1,23 @@ -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_b" -declared at annotate_ignore_write.c:11 - -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_c" -declared at annotate_ignore_write.c:12 - -Conflicting store by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_a" -declared at annotate_ignore_write.c:10 -Finished. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -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 2014-06-15 20:37:07.083126436 -0500 +++ annotate_ignore_write2.stderr.out 2014-06-15 21:12:07.687494398 -0500 @@ -1,24 +1,23 @@ -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_b" -declared at annotate_ignore_write.c:11 - -Conflicting store by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_a" -declared at annotate_ignore_write.c:10 - -Conflicting load by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_c" -declared at annotate_ignore_write.c:12 - -Conflicting store by thread 1 at 0x........ size 1 - at 0x........: main (annotate_ignore_write.c:?) -Location 0x........ is 0 bytes inside global var "s_a" -declared at annotate_ignore_write.c:10 -Finished. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -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 2014-06-15 20:37:07.076126355 -0500 +++ annotate_order_1.stderr.out 2014-06-15 21:12:07.848496266 -0500 @@ -1,6 +1,23 @@ -FLAGS [phb=1, fm=0] -test03: negative - GLOB=2 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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 2014-06-15 20:37:07.246128327 -0500 +++ annotate_order_2.stderr.out 2014-06-15 21:12:08.017498227 -0500 @@ -1,6 +1,23 @@ -FLAGS [phb=1, fm=0] -test30: negative - GLOB=47 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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 2014-06-15 20:37:07.162127353 -0500 +++ annotate_order_3.stderr.out 2014-06-15 21:12:08.182500141 -0500 @@ -1,6 +1,23 @@ -FLAGS [phb=1, fm=0] -test31: negative - GLOB=48 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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 2014-06-15 20:37:07.109126738 -0500 +++ annotate_publish_hg.stderr.out 2014-06-15 21:12:08.363502240 -0500 @@ -1,7 +1,23 @@ -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_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_rwlock.stderr.diff ================================================= --- annotate_rwlock.stderr.exp 2014-06-15 20:37:07.061126181 -0500 +++ annotate_rwlock.stderr.out 2014-06-15 21:12:08.513503980 -0500 @@ -1,4 +1,23 @@ -Finished. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_rwlock_hg.stderr.diff ================================================= --- annotate_rwlock_hg.stderr.exp 2014-06-15 20:37:07.123126901 -0500 +++ annotate_rwlock_hg.stderr.out 2014-06-15 21:12:08.577504723 -0500 @@ -1 +0,0 @@ -Total error count is below threshold. ================================================= ./valgrind-new/drd/tests/annotate_sem.stderr.diff ================================================= --- annotate_sem.stderr.exp 2014-06-15 20:37:07.087126483 -0500 +++ annotate_sem.stderr.out 2014-06-15 21:12:08.726506451 -0500 @@ -1,4 +1,23 @@ -Finished. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_smart_pointer.stderr.diff ================================================= --- annotate_smart_pointer.stderr.exp 2014-06-15 20:37:07.098126610 -0500 +++ annotate_smart_pointer.stderr.out 2014-06-15 21:12:08.867508087 -0500 @@ -1,4 +1,23 @@ -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_smart_pointer2.stderr.diff ================================================= --- annotate_smart_pointer2.stderr.exp 2014-06-15 20:37:07.190127678 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 21:12:09.125511080 -0500 @@ -1,13 +1,23 @@ -Conflicting store by thread x at 0x........ size 4 - at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?) - by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?) - by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?) - by 0x........: main (annotate_smart_pointer.cpp:?) -Address 0x........ is at offset ... from 0x......... Allocation context: - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (annotate_smart_pointer.cpp:?) -Done. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_smart_pointer2.stderr.diff-darwin ================================================= --- annotate_smart_pointer2.stderr.exp-darwin 2014-06-15 20:37:07.245128316 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 21:12:09.125511080 -0500 @@ -1,14 +1,23 @@ -Conflicting store by thread x at 0x........ size 4 - at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?) - by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?) - by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?) - by 0x........: main (annotate_smart_pointer.cpp:?) -Address 0x........ is at offset ... from 0x......... Allocation context: - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: operator new(unsigned long) (in /usr/lib/libstdc++.6.0.9.dylib) - by 0x........: main (annotate_smart_pointer.cpp:?) -Done. +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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. -ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/drd/tests/annotate_spinlock.stderr.diff ================================================= --- annotate_spinlock.stderr.exp 2014-06-15 20:37:07.108126726 -0500 +++ annotate_spinlock.stderr.out 2014-06-15 21:12:09.306513180 -0500 @@ -1,6 +1,23 @@ -FLAGS [phb=1, fm=0] -test27: negative - GLOB=4 -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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 2014-06-15 20:37:07.212127933 -0500 +++ annotate_static.stderr.out 2014-06-15 21:12:09.450514850 -0500 @@ -1,4 +1,23 @@ -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_trace_memory.stderr.diff-32bit ================================================= --- annotate_trace_memory.stderr.exp-32bit 2014-06-15 20:37:07.118126843 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -0500 @@ -1,52 +1,23 @@ -float -store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -double -store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 8 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint8_t -store 0x........ size 1 val 5/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 1 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 1 val 11/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint16_t -store 0x........ size 2 val 7/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 2 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 2 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint32_t -store 0x........ size 4 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint64_t -store 0x........ size 4 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 305419905/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_trace_memory.stderr.diff-64bit ================================================= --- annotate_trace_memory.stderr.exp-64bit 2014-06-15 20:37:07.154127260 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -0500 @@ -1,46 +1,23 @@ -float -store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -double -store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 8 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint8_t -store 0x........ size 1 val 5/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 1 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 1 val 11/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint16_t -store 0x........ size 2 val 7/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 2 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 2 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint32_t -store 0x........ size 4 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint64_t -store 0x........ size 8 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 8 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 8 val 305419905/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_trace_memory.stderr.diff-mips32 ================================================= --- annotate_trace_memory.stderr.exp-mips32 2014-06-15 20:37:07.041125949 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -0500 @@ -1,58 +1,23 @@ -float -store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -double -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 1074266112/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 1075576832/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint8_t -store 0x........ size 1 val 5/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 1 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 1 val 11/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint16_t -store 0x........ size 2 val 7/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 2 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 2 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint32_t -store 0x........ size 4 val 8/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -uint64_t -store 0x........ size 4 val 9/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -load 0x........ size 4 (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 305419905/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -store 0x........ size 4 val 0/0x........ (thread x / vc ...) - at 0x........: main (annotate_trace_memory.c:?) -Done. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed. + +host stacktrace: + at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-new/drd/drd-amd64-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_trace_memory_xml.stderr.diff-32bit ================================================= --- annotate_trace_memory_xml.stderr.exp-32bit 2014-06-15 20:37:07.112126773 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 21:12:09.819519131 -0500 @@ -23,280 +23,26 @@ </argv> </args> -<status> - <state>RUNNING</state> - <time>...</time> -</status> +</valgrindoutput> -float - <trace><text>store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 4 (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> -double - <trace><text>store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 8 (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> -uint8_t - <trace><text>store 0x........ size 1 val 5/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 1 (thread x / vc ...)</text> <truncated beyond 100 lines> ================================================= ./valgrind-new/drd/tests/annotate_trace_memory_xml.stderr.diff-64bit ================================================= --- annotate_trace_memory_xml.stderr.exp-64bit 2014-06-15 20:37:07.147127179 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 21:12:09.819519131 -0500 @@ -23,244 +23,26 @@ </argv> </args> -<status> - <state>RUNNING</state> - <time>...</time> -</status> - -float - <trace><text>store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 4 (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> -double - <trace><text>store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 8 (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> -uint8_t - <trace><text>store 0x........ size 1 val 5/0x........ (thread x / vc ...)</text> - <stack> - <frame> - <ip>0x........</ip> - <obj>...</obj> - <fn>main</fn> - <dir>...</dir> - <file>annotate_trace_memory.c</file> - <line>...</line> - </frame> - </stack> - </trace> - <trace><text>load 0x........ size 1 (thread x / vc ...)</text> - <stack> <truncated beyond 100 lines> ================================================= ./valgrind-new/drd/tests/annotate_trace_memory_xml.stderr.diff-mips32 ================================================= --- annotate_trace_memory_xml.stderr.exp-mips32 2014-06-15 20:37:07.294128884 -0500 +++ annotate_trace_memory_xml.... [truncated message content] |