================================================= ./valgrind-new/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-04-24 10:13:54.870371584 +0100 +++ preen_invars.stderr.out 2014-04-24 10:35:17.726099470 +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:308) + by 0x........: report_and_quit (m_libcassert.c:367) + by 0x........: vgPlain_assert_fail (m_libcassert.c:432) + 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-04-24 10:13:54.865371676 +0100 +++ preen_invars.stdout.out 2014-04-24 10:35:14.320163633 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-new/gdbserver_tests/mcinfcallRU.stderr.diff ================================================= --- mcinfcallRU.stderr.exp 2014-04-24 10:13:43.841573665 +0100 +++ mcinfcallRU.stderr.out 2014-04-24 10:21:18.721018764 +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-04-24 10:13:43.869573153 +0100 +++ mcinfcallWSRU.stderr.out 2014-04-24 10:21:21.217971225 +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-04-24 10:13:43.858573354 +0100 +++ mcmain_pic.stderr.out 2014-04-24 10:21:38.029651488 +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=0F +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=0F +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/gdbserver_tests/nlgone_exit.stdoutB.diff ================================================= --- nlgone_exit.stdoutB.exp 2014-04-24 10:13:43.866573208 +0100 +++ nlgone_exit.stdoutB.out 2014-04-24 10:21:59.229247350 +0100 @@ -1,5 +1,6 @@ Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in syscall ... +0x........ in __GI__exit (status=status@entry=1) +33 INLINE_SYSCALL (exit_group, 1, status); Continuing. Program exited with code 01. ================================================= ./valgrind-new/memcheck/tests/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2014-04-24 10:13:56.338344650 +0100 +++ err_disable4.stderr.out 2014-04-24 10:23:13.407828141 +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. @@ -1426,87 +1427,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. - --------- Letting 498 threads make an error ------ - -Thread x: -Invalid read of size 1 - at 0x........: err (err_disable4.c:41) - by 0x........: child_fn_2 (err_disable4.c:55) - ... - Address 0x........ is 5 bytes inside a block of size 10 free'd - at 0x........: free (vg_replace_malloc.c:...) - by 0x........: main (err_disable4.c:68) - - --------- Got 498 errors (expected 498 ==> PASS) ------ - ================================================= ./valgrind-new/none/tests/fdleak_ipv4.stderr.diff ================================================= --- fdleak_ipv4.stderr.exp 2014-04-24 10:13:51.140439982 +0100 +++ fdleak_ipv4.stderr.out 2014-04-24 10:27:05.264433024 +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-new/none/tests/fdleak_ipv4.stdout.diff ================================================= --- fdleak_ipv4.stdout.exp 2014-04-24 10:13:53.256401186 +0100 +++ fdleak_ipv4.stdout.out 2014-04-24 10:26:55.009626421 +0100 @@ -1 +0,0 @@ -hello ================================================= ./valgrind-old/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-04-24 08:52:40.282309505 +0100 +++ preen_invars.stderr.out 2014-04-24 10:13:29.259840009 +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:308) + by 0x........: report_and_quit (m_libcassert.c:367) + by 0x........: vgPlain_assert_fail (m_libcassert.c:432) + 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-04-24 08:52:40.278309583 +0100 +++ preen_invars.stdout.out 2014-04-24 10:13:25.907901078 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-old/gdbserver_tests/mcinfcallRU.stderr.diff ================================================= --- mcinfcallRU.stderr.exp 2014-04-24 08:52:29.691515578 +0100 +++ mcinfcallRU.stderr.out 2014-04-24 09:06:11.322658632 +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-04-24 08:52:29.701515384 +0100 +++ mcinfcallWSRU.stderr.out 2014-04-24 09:06:14.111604974 +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-04-24 08:52:29.700515403 +0100 +++ mcmain_pic.stderr.out 2014-04-24 09:06:31.844263819 +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=0F +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=0F +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/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff ================================================= --- nlvgdbsigqueue.stdoutB.exp 2014-04-24 08:52:29.695515501 +0100 +++ nlvgdbsigqueue.stdoutB.out 2014-04-24 09:07:17.092393343 +0100 @@ -1,14 +1,13 @@ continuing to have vgdb interrupted by simulate_control_c Continuing. -Program received signal SIGUSR1, User defined signal 1. +Program received signal SIGTRAP, Trace/breakpoint trap. 0x........ in syscall ... continuing to receive first SIGUSR1 Continuing. -[New Thread ....] Program received signal SIGUSR1, User defined signal 1. 0x........ in syscall ... continuing to receive second SIGUSR1 Continuing. -Program received signal SIGTRAP, Trace/breakpoint trap. +Program received signal SIGUSR1, User defined signal 1. 0x........ in syscall ... Kill the program being debugged? (y or n) [answered Y; input not from terminal]