================================================= ./valgrind-new/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-08-14 03:12:09.349107841 +0100 +++ preen_invars.stderr.out 2014-08-14 03:31:19.400093048 +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-14 03:12:09.353107764 +0100 +++ preen_invars.stdout.out 2014-08-14 03:31:16.099156236 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-new/gdbserver_tests/mcinfcallRU.stderr.diff ================================================= --- mcinfcallRU.stderr.exp 2014-08-14 03:12:08.164130524 +0100 +++ mcinfcallRU.stderr.out 2014-08-14 03:17:31.789935534 +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-14 03:12:08.174130333 +0100 +++ mcinfcallWSRU.stderr.out 2014-08-14 03:17:35.365867082 +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-14 03:12:08.173130352 +0100 +++ mcmain_pic.stderr.out 2014-08-14 03:17:49.991587109 +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-14 03:12:08.675120743 +0100 +++ err_disable4.stderr.out 2014-08-14 03:19:05.871134589 +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. @@ -289,1224 +290,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-14 03:12:08.531123499 +0100 +++ vbit-test.stderr.out 2014-08-14 03:21:12.542709785 +0100 @@ -0,0 +1 @@ +unknown opcode 5918 ================================================= ./valgrind-old/drd/tests/pth_spinlock.stderr.diff ================================================= --- pth_spinlock.stderr.exp 2014-08-14 02:52:21.528845630 +0100 +++ pth_spinlock.stderr.out 2014-08-14 03:09:27.578204532 +0100 @@ -1,5 +1,43 @@ Start of test. -Test successful. -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +drd: drd_thread.c:292 (vgDrd_thread_pre_create): Assertion 'DRD_(VgThreadIdToDrdThreadId)(vg_created) == DRD_INVALID_THREADID' failed. + +host stacktrace: + at 0x........: show_sched_status_wrk (m_libcassert.c:?) + by 0x........: report_and_quit (m_libcassert.c:?) + by 0x........: vgPlain_assert_fail (m_libcassert.c:?) + by 0x........: vgDrd_thread_pre_create (drd_thread.c:?) + by 0x........: drd_pre_thread_create (drd_main.c:?) + by 0x........: vgSysWrap_amd64_linux_sys_clone_before (syswrap-amd64-linux.c:294) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1586) + by 0x........: handle_syscall (scheduler.c:?) + by 0x........: vgPlain_scheduler (scheduler.c:?) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:103) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: clone (in /...libc...) + by 0x........: do_clone.constprop.4 (createthread.c:?) + by 0x........: pthread_create@@GLIBC_2.2.5 (createthread.c:?) + by 0x........: pthread_create (drd_pthread_intercepts.c:?) + by 0x........: main (pth_spinlock.c:?) + +Thread 2: status = VgTs_Init + at 0x........: clone (in /...libc...) + + +Note: see also the FAQ in the source distribution. +It contains workarounds to several common problems. +In particular, if Valgrind aborted or crashed after +identifying problems in your program, there's a good chance +that fixing those problems will prevent Valgrind aborting or +crashing, especially if it happened in m_mallocfree.c. + +If that doesn't help, please report this bug to: www.valgrind.org + +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. + ================================================= ./valgrind-old/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-08-14 02:53:27.831576434 +0100 +++ preen_invars.stderr.out 2014-08-14 03:11:49.077495889 +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-old/exp-sgcheck/tests/preen_invars.stdout.diff ================================================= --- preen_invars.stdout.exp 2014-08-14 02:53:27.834576376 +0100 +++ preen_invars.stdout.out 2014-08-14 03:11:46.229550406 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-old/gdbserver_tests/mcinfcallRU.stderr.diff ================================================= --- mcinfcallRU.stderr.exp 2014-08-14 02:53:19.950727292 +0100 +++ mcinfcallRU.stderr.out 2014-08-14 02:58:42.084560862 +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-old/gdbserver_tests/mcinfcallWSRU.stderr.diff ================================================= --- mcinfcallWSRU.stderr.exp 2014-08-14 02:53:19.979726737 +0100 +++ mcinfcallWSRU.stderr.out 2014-08-14 02:58:45.652492563 +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-old/gdbserver_tests/mcmain_pic.stderr.diff ================================================= --- mcmain_pic.stderr.exp 2014-08-14 02:53:19.968726948 +0100 +++ mcmain_pic.stderr.out 2014-08-14 02:58:59.220232843 +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-old/memcheck/tests/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2014-08-14 02:51:26.109906485 +0100 +++ err_disable4.stderr.out 2014-08-14 03:00:13.020820119 +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. @@ -325,1188 +326,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-old/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2014-08-14 02:51:14.979119555 +0100 +++ vbit-test.stderr.out 2014-08-14 03:02:20.456380690 +0100 @@ -0,0 +1 @@ +unknown opcode 5918 ================================================= ./valgrind-old/none/tests/fdleak_ipv4.stderr.diff ================================================= --- fdleak_ipv4.stderr.exp 2014-08-14 02:53:06.008994171 +0100 +++ fdleak_ipv4.stderr.out 2014-08-14 03:04:08.376314838 +0100 @@ -17,11 +17,9 @@ +connect: Connection refused -FILE DESCRIPTORS: 4 open at exit. -Open AF_INET socket 3: 127.0.0.1:... <-> 127.0.0.1:... - ... - +FILE DESCRIPTORS: 3 open at exit. Open file descriptor ...: ... ================================================= ./valgrind-old/none/tests/fdleak_ipv4.stdout.diff ================================================= --- fdleak_ipv4.stdout.exp 2014-08-14 02:53:02.596059503 +0100 +++ fdleak_ipv4.stdout.out 2014-08-14 03:03:58.115511255 +0100 @@ -1 +0,0 @@ -hello