================================================= ./valgrind-new/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-04-24 10:13:55.581358539 +0100 +++ preen_invars.stderr.out 2014-04-24 10:35:08.772268145 +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:42) + by 0x........: _dl_close_worker (dl-close.c:225) + by 0x........: _dl_close (dl-close.c:776) + by 0x........: _dl_catch_error (dl-error.c:177) + by 0x........: _dlerror_run (dlerror.c:163) + by 0x........: dlclose (dlclose.c:47) + 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:55.584358485 +0100 +++ preen_invars.stdout.out 2014-04-24 10:35:05.427331155 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-new/gdbserver_tests/nlgone_exit.stdoutB.diff ================================================= --- nlgone_exit.stdoutB.exp 2014-04-24 10:13:55.000369199 +0100 +++ nlgone_exit.stdoutB.out 2014-04-24 10:22:02.844178050 +0100 @@ -1,5 +1,6 @@ Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in syscall ... +0x........ in __GI__exit (status=status@entry=1) +32 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:55.909352522 +0100 +++ err_disable4.stderr.out 2014-04-24 10:23:13.329829653 +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. @@ -658,855 +659,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/none/tests/fdleak_ipv4.stderr.diff ================================================= --- fdleak_ipv4.stderr.exp 2014-04-24 10:13:51.839427168 +0100 +++ fdleak_ipv4.stderr.out 2014-04-24 10:26:55.282621272 +0100 @@ -1,10 +1,8 @@ +bind(s, (struct sockaddr *)&addr, sizeof(addr)): Address already in use -FILE DESCRIPTORS: 5 open at exit. -Open AF_INET socket 4: 127.0.0.1:... <-> 127.0.0.1:... - ... - -Open AF_INET socket 3: 127.0.0.1:... <-> unbound +FILE DESCRIPTORS: 4 open at exit. +Open AF_INET socket 3: <-> unbound ... Open file descriptor ...: ... ================================================= ./valgrind-old/exp-sgcheck/tests/preen_invars.stderr.diff-glibc28-amd64 ================================================= --- preen_invars.stderr.exp-glibc28-amd64 2014-04-24 08:52:57.613972480 +0100 +++ preen_invars.stderr.out 2014-04-24 10:13:18.981027065 +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:42) + by 0x........: _dl_close_worker (dl-close.c:225) + by 0x........: _dl_close (dl-close.c:776) + by 0x........: _dl_catch_error (dl-error.c:177) + by 0x........: _dlerror_run (dlerror.c:163) + by 0x........: dlclose (dlclose.c:47) + 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:57.609972558 +0100 +++ preen_invars.stdout.out 2014-04-24 10:13:15.592088592 +0100 @@ -1 +0,0 @@ -foo bar 1 ================================================= ./valgrind-old/none/tests/fdleak_ipv4.stderr.diff ================================================= --- fdleak_ipv4.stderr.exp 2014-04-24 08:52:56.570992754 +0100 +++ fdleak_ipv4.stderr.out 2014-04-24 10:04:54.372465073 +0100 @@ -1,10 +1,8 @@ +bind(s, (struct sockaddr *)&addr, sizeof(addr)): Address already in use -FILE DESCRIPTORS: 5 open at exit. -Open AF_INET socket 4: 127.0.0.1:... <-> 127.0.0.1:... - ... - -Open AF_INET socket 3: 127.0.0.1:... <-> unbound +FILE DESCRIPTORS: 4 open at exit. +Open AF_INET socket 3: <-> unbound ... Open file descriptor ...: ...