================================================= ./valgrind-new/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-08-10 02:52:02.188849173 +0100 +++ preen_invars.stderr.out 2014-08-10 03:09:53.094349418 +0100 @@ -6,4 +6,39 @@ Actual: global array "im_a_global_arr" of size 10 in object with soname "preen_invars_so" -ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) +exp-sgcheck: sg_main.c:560 (add_blocks_to_StackTree): Assertion '!already_present' failed. + +host stacktrace: + at 0x........: show_sched_status_wrk (m_libcassert.c:317) + by 0x........: report_and_quit (m_libcassert.c:376) + by 0x........: vgPlain_assert_fail (m_libcassert.c:441) + by 0x........: add_blocks_to_StackTree (sg_main.c:560) + by 0x........: shadowStack_new_frame.isra.12 (sg_main.c:1875) + by 0x........: ??? + by 0x........: ??? + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: _dl_sort_fini (dl-fini.c:43) + by 0x........: _dl_close_worker (dl-close.c:226) + by 0x........: _dl_close (dl-close.c:773) + by 0x........: _dl_catch_error (dl-error.c:178) + by 0x........: _dlerror_run (dlerror.c:164) + by 0x........: dlclose (dlclose.c:48) + by 0x........: main (preen_invars.c:48) + + +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/exp-sgcheck/tests/preen_invars.stdout.diff ================================================= --- preen_invars.stdout.exp 2014-08-10 02:52:02.183849268 +0100 +++ preen_invars.stdout.out 2014-08-10 03:09:50.357401810 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-new/gdbserver_tests/mcinfcallRU.stderr.diff ================================================= --- mcinfcallRU.stderr.exp 2014-08-10 02:52:01.194868200 +0100 +++ mcinfcallRU.stderr.out 2014-08-10 02:57:09.790960915 +0100 @@ -1,4 +1,12 @@ loops/sleep_ms/burn/threads_spec: 1 0 2000000000 ------B- main ready to sleep and/or burn +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 pid .... Thread .... inferior call pushed from gdb in mcinfcallRU.stdinB.gdb +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-new/gdbserver_tests/mcinfcallWSRU.stderr.diff ================================================= --- mcinfcallWSRU.stderr.exp 2014-08-10 02:52:01.176868544 +0100 +++ mcinfcallWSRU.stderr.out 2014-08-10 02:57:13.307893592 +0100 @@ -3,5 +3,13 @@ London ready to sleep and/or burn Petaouchnok ready to sleep and/or burn main ready to sleep and/or burn +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 pid .... Thread .... thread 1 inferior call pushed from gdb in mcinfcallWSRU.stdinB.gdb +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-new/gdbserver_tests/mcmain_pic.stderr.diff ================================================= --- mcmain_pic.stderr.exp 2014-08-10 02:52:01.201868066 +0100 +++ mcmain_pic.stderr.out 2014-08-10 02:57:27.204627574 +0100 @@ -2,6 +2,14 @@ (action at startup) vgdb me ... +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 +vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=NONE +vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 HEAP SUMMARY: in use at exit: 16 bytes in 1 blocks ================================================= ./valgrind-new/memcheck/tests/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2014-08-10 02:52:01.402864218 +0100 +++ err_disable4.stderr.out 2014-08-10 02:58:38.474263299 +0100 @@ -1,6 +1,7 @@ -------- Letting 498 threads exit w/ errs disabled ------ +err_disable4: err_disable4.c:85: main: Assertion `!r' failed. WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. @@ -670,843 +671,3 @@ WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use ================================================= ./valgrind-new/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2014-08-10 02:52:01.798856638 +0100 +++ vbit-test.stderr.out 2014-08-10 03:00:42.505889030 +0100 @@ -0,0 +1 @@ +unknown opcode 5918