================================================= ./valgrind-new/drd/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-23 03:55:37.759157712 +0200 +++ threaded-fork.stderr.out 2012-10-23 04:05:56.959187421 +0200 @@ -1,6 +1,30 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:?) + by 0x........: vgPlain_assert_fail (m_libcassert.c:?) + by 0x........: handle_syscall (scheduler.c:?) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: main (threaded-fork.c:28) + + +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. + PASS ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/gdbserver_tests/mcclean_after_fork.stderr.diff ================================================= --- mcclean_after_fork.stderr.exp 2012-10-23 03:55:35.169157554 +0200 +++ mcclean_after_fork.stderr.out 2012-10-23 03:56:55.559161960 +0200 @@ -3,14 +3,31 @@ +valgrind: m_mallocfree.c:268 (mk_plain_bszB): Assertion 'bszB != 0' failed. +valgrind: This is probably caused by your program erroneously writing past the +end of a heap block and corrupting heap metadata. If you fix any +invalid writes reported by Memcheck, this assertion failure will +probably go away. Please try that before reporting this as a bug. + ... -HEAP SUMMARY: - in use at exit: 0 bytes in 0 blocks - total heap usage: 0 allocs, 0 frees, 0 bytes allocated +sched status: + running_tid=1 -For a detailed leak analysis, rerun with: --leak-check=full +Thread 1: status = VgTs_Runnable + ... + + +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. -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-new/gdbserver_tests/mcclean_after_fork.stdoutB.diff ================================================= --- mcclean_after_fork.stdoutB.exp 2012-10-23 03:55:35.169157554 +0200 +++ mcclean_after_fork.stdoutB.out 2012-10-23 03:56:55.599161962 +0200 @@ -7,6 +7,6 @@ Hardware read watchpoint 4: mem Continuing. Hardware read watchpoint 4: mem -Value = 0 +Value = 256 main () at clean_after_fork.c:34 34 if (mem == 0) ================================================= ./valgrind-new/gdbserver_tests/nlpasssigalrm.stderr.diff ================================================= --- nlpasssigalrm.stderr.exp 2012-10-23 03:55:35.169157554 +0200 +++ nlpasssigalrm.stderr.out 2012-10-23 03:57:35.579163135 +0200 @@ -6,5 +6,31 @@ starting ... ok: 1st SIGALRM received ok: 2nd SIGALRM received + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x4010B270A: report_and_quit (m_libcassert.c:235) + by 0x4010B289B: vgPlain_assert_fail (m_libcassert.c:309) + by 0x40107671D: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x40A1788: do_system (in /...libc...) + by 0x80000B69: main (passsigalrm.c:52) + + +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. + ok: SIGRTMIN received ================================================= ./valgrind-new/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-10-23 03:55:34.969157544 +0200 +++ tc18_semabuse.stderr.out 2012-10-23 04:02:29.729177684 +0200 @@ -21,7 +21,7 @@ ---------------------------------------------------------------- Thread #x's call to sem_post failed - with error code 22 (EINVAL: Invalid argument) + with error code 38 (ENOSYS: Function not implemented) at 0x........: sem_post_WRK (hg_intercepts.c:...) by 0x........: sem_post (hg_intercepts.c:...) by 0x........: main (tc18_semabuse.c:37) ================================================= ./valgrind-new/helgrind/tests/tc18_semabuse.stderr.diff-linux-mips32 ================================================= --- tc18_semabuse.stderr.exp-linux-mips32 2012-10-23 03:55:34.969157544 +0200 +++ tc18_semabuse.stderr.out 2012-10-23 04:02:29.729177684 +0200 @@ -18,5 +18,13 @@ by 0x........: sem_wait (hg_intercepts.c:...) by 0x........: main (tc18_semabuse.c:34) +---------------------------------------------------------------- -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) +Thread #x's call to sem_post failed + with error code 38 (ENOSYS: Function not implemented) + at 0x........: sem_post_WRK (hg_intercepts.c:...) + by 0x........: sem_post (hg_intercepts.c:...) + by 0x........: main (tc18_semabuse.c:37) + + +ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/helgrind/tests/tc20_verifywrap.stderr.diff ================================================= --- tc20_verifywrap.stderr.exp 2012-10-23 03:55:34.969157544 +0200 +++ tc20_verifywrap.stderr.out 2012-10-23 04:02:35.149177950 +0200 @@ -218,7 +218,7 @@ ---------------------------------------------------------------- Thread #x's call to sem_post failed - with error code 22 (EINVAL: Invalid argument) + with error code 38 (ENOSYS: Function not implemented) at 0x........: sem_post_WRK (hg_intercepts.c:...) by 0x........: sem_post (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:245) ================================================= ./valgrind-new/helgrind/tests/tc20_verifywrap.stderr.diff-mips32 ================================================= --- tc20_verifywrap.stderr.exp-mips32 2012-10-23 03:55:34.969157544 +0200 +++ tc20_verifywrap.stderr.out 2012-10-23 04:02:35.149177950 +0200 @@ -35,7 +35,7 @@ ---------------------------------------------------------------- Thread #x's call to pthread_join failed - with error code 45 (EDEADLK: Resource deadlock would occur) + with error code 35 (EDEADLK: Resource deadlock would occur) at 0x........: pthread_join_WRK (hg_intercepts.c:...) by 0x........: pthread_join (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:83) @@ -46,7 +46,7 @@ ---------------------------------------------------------------- Thread #x's call to pthread_mutex_init failed - with error code 122 (EOPNOTSUPP: Operation not supported on transport endpoint) + with error code 95 (EOPNOTSUPP: Operation not supported on transport endpoint) at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:92) @@ -215,6 +215,14 @@ by 0x........: sem_wait (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:242) +---------------------------------------------------------------- + +Thread #x's call to sem_post failed + with error code 38 (ENOSYS: Function not implemented) + at 0x........: sem_post_WRK (hg_intercepts.c:...) + by 0x........: sem_post (hg_intercepts.c:...) + by 0x........: main (tc20_verifywrap.c:245) + FIXME: can't figure out how to verify wrap of sem_post @@ -227,4 +235,4 @@ ... -ERROR SUMMARY: 22 errors from 22 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 23 errors from 23 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/memcheck/tests/addressable.stderr.diff ================================================= --- addressable.stderr.exp 2012-10-23 03:55:35.619157584 +0200 +++ addressable.stderr.out 2012-10-23 03:57:42.799163274 +0200 @@ -38,48 +38,77 @@ For counts of detected and suppressed errors, rerun with: -v ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... -For a detailed leak analysis, rerun with: --leak-check=full +sched status: + running_tid=0 -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +Thread 1: status = VgTs_Runnable + ... + by 0x........: main (addressable.c:119) -Process terminating with default action of signal N (SIGSEGV or SIGBUS) - Bad memory (SIGSEGV or SIGBUS) at address 0x........ - at 0x........: test4 (addressable.c:74) - by 0x........: main (addressable.c:125) -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated +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. -For a detailed leak analysis, rerun with: --leak-check=full +If that doesn't help, please report this bug to: www.valgrind.org -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -Uninitialised byte(s) found during client check request - at 0x........: test5 (addressable.c:85) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd - -Uninitialised byte(s) found during client check request - at 0x........: test5 (addressable.c:91) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... -For a detailed leak analysis, rerun with: --leak-check=full +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: main (addressable.c:119) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: main (addressable.c:119) + + +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. ================================================= ./valgrind-new/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-10-23 03:55:35.679157587 +0200 +++ addressable.stdout.out 2012-10-23 03:57:42.759163272 +0200 @@ -1,5 +1,5 @@ Test 1: PASS Test 2: PASS -Test 3: PASS -Test 4: PASS -Test 5: PASS +Test 3: exited with unexpected status 1 +Test 4: exited with unexpected status 1 +Test 5: exited with unexpected status 1 ================================================= ./valgrind-new/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2012-10-23 03:55:35.199157556 +0200 +++ vbit-test.stderr.out 2012-10-23 03:59:47.899170002 +0200 @@ -0,0 +1,273 @@ + +valgrind: m_scheduler/scheduler.c:547 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_WaitSys + ... + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + + +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: m_scheduler/scheduler.c:547 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_WaitSys + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-new/memcheck/tests/vbit-test/vbit-test) + + +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/none/tests/allexec32.stderr.diff ================================================= --- allexec32.stderr.exp 2012-10-23 03:55:37.329157689 +0200 +++ allexec32.stderr.out 2012-10-23 04:00:17.239171555 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) +sched status: + running_tid=1 +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:40) +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:24) + by 0x........: main (allexec.c:40) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:22) + by 0x........: main (allexec.c:42) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:42) + ================================================= ./valgrind-new/none/tests/allexec32.stdout.diff ================================================= --- allexec32.stdout.exp 2012-10-23 03:55:37.329157689 +0200 +++ allexec32.stdout.out 2012-10-23 04:00:17.219171554 +0200 @@ -1,14 +1,9 @@ ./allexec32 will exec ./allexec32 program exec-ed: ./allexec32 child exited -program exec-ed: ./allexec32 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec32 child exited ./allexec32 will exec ./allexec64 -program exec-ed: ./allexec64 child exited -program exec-ed: ./allexec64 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec64 child exited ================================================= ./valgrind-new/none/tests/allexec64.stderr.diff ================================================= --- allexec64.stderr.exp 2012-10-23 03:55:37.359157690 +0200 +++ allexec64.stderr.out 2012-10-23 04:00:17.629171581 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) +sched status: + running_tid=1 +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:40) +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:24) + by 0x........: main (allexec.c:40) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:22) + by 0x........: main (allexec.c:42) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:42) + ================================================= ./valgrind-new/none/tests/allexec64.stdout.diff ================================================= --- allexec64.stdout.exp 2012-10-23 03:55:37.379157691 +0200 +++ allexec64.stdout.out 2012-10-23 04:00:17.609171580 +0200 @@ -1,14 +1,9 @@ ./allexec64 will exec ./allexec32 program exec-ed: ./allexec32 child exited -program exec-ed: ./allexec32 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec32 child exited ./allexec64 will exec ./allexec64 -program exec-ed: ./allexec64 child exited -program exec-ed: ./allexec64 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec64 child exited ================================================= ./valgrind-new/none/tests/async-sigs.stderr.diff ================================================= --- async-sigs.stderr.exp 2012-10-23 03:55:37.329157689 +0200 +++ async-sigs.stderr.out 2012-10-23 04:00:18.629171648 +0200 @@ -1,8 +1,30 @@ -testing: blocking=0 caught=11 fatal=7... PASSED -testing: blocking=0 caught=11 fatal=1... PASSED -testing: blocking=0 caught=10 fatal=7... PASSED -testing: blocking=0 caught=10 fatal=1... PASSED -testing: blocking=1 caught=11 fatal=7... PASSED -testing: blocking=1 caught=11 fatal=1... PASSED -testing: blocking=1 caught=10 fatal=7... PASSED -testing: blocking=1 caught=10 fatal=1... PASSED +testing: blocking=0 caught=11 fatal=7... +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_kill (async-sigs.c:53) + by 0x........: test (async-sigs.c:105) + by 0x........: main (async-sigs.c:129) + + +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. + +kill 24465 failed status=exit 1 ================================================= ./valgrind-new/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-10-23 03:55:37.329157689 +0200 +++ async-sigs.stderr.out 2012-10-23 04:00:18.629171648 +0200 @@ -1,8 +1,30 @@ -testing: blocking=0 caught=11 fatal=10... PASSED -testing: blocking=0 caught=11 fatal=1... PASSED -testing: blocking=0 caught=16 fatal=10... PASSED -testing: blocking=0 caught=16 fatal=1... PASSED -testing: blocking=1 caught=11 fatal=10... PASSED -testing: blocking=1 caught=11 fatal=1... PASSED -testing: blocking=1 caught=16 fatal=10... PASSED -testing: blocking=1 caught=16 fatal=1... PASSED +testing: blocking=0 caught=11 fatal=7... +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_kill (async-sigs.c:53) + by 0x........: test (async-sigs.c:105) + by 0x........: main (async-sigs.c:129) + + +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. + +kill 24465 failed status=exit 1 ================================================= ./valgrind-new/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-10-23 03:55:37.379157691 +0200 +++ exec-sigmask.stderr.out 2012-10-23 04:00:20.679171784 +0200 @@ -1,2 +1,31 @@ +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_exec (exec-sigmask.c:15) + by 0x........: main (exec-sigmask.c:51) + + +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. + +child exec failed + ================================================= ./valgrind-new/none/tests/pth_atfork1.stderr.diff ================================================= --- pth_atfork1.stderr.exp 2012-10-23 03:55:37.319157688 +0200 +++ pth_atfork1.stderr.out 2012-10-23 04:00:36.439172678 +0200 @@ -1,3 +1,31 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=2 + +Thread 2: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: thread (pth_atfork1.c:101) + by 0x........: start_thread (in /lib64/libpthread-2.14.1.so) + by 0x........: ??? (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. + +./pth_atfork1: pthread_join res != 0 ================================================= ./valgrind-new/none/tests/pth_atfork1.stdout.diff ================================================= --- pth_atfork1.stdout.exp 2012-10-23 03:55:37.329157689 +0200 +++ pth_atfork1.stdout.out 2012-10-23 04:00:36.229172664 +0200 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-new/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-10-23 03:55:37.329157689 +0200 +++ shell.stderr.out 2012-10-23 04:01:14.039174590 +0200 @@ -1,8 +1,253 @@ ./shell: ./x86/: is a directory -./shell: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell: ./shell_binaryfile: cannot execute binary file -./shell: ./shell_nosuchfile: No such file or directory -./shell: shell_nosuchfile: command not found + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/shell.stderr.diff-dash ================================================= --- shell.stderr.exp-dash 2012-10-23 03:55:37.329157689 +0200 +++ shell.stderr.out 2012-10-23 04:01:14.039174590 +0200 @@ -1,8 +1,253 @@ -./shell: 10: ./x86/: Permission denied -./shell: 13: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell_binaryfile: 4: Syntax error: ")" unexpected -./shell: 22: ./shell_nosuchfile: not found -./shell: 25: shell_nosuchfile: not found +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/shell.stderr.diff-dash2 ================================================= --- shell.stderr.exp-dash2 2012-10-23 03:55:37.329157689 +0200 +++ shell.stderr.out 2012-10-23 04:01:14.039174590 +0200 @@ -1,8 +1,253 @@ -./shell: 10: ./shell: ./x86/: Permission denied -./shell: 13: ./shell: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell_binaryfile: 4: ./shell_binaryfile: Syntax error: ")" unexpected -./shell: 22: ./shell: ./shell_nosuchfile: not found -./shell: 25: ./shell: shell_nosuchfile: not found +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/syscall-restart2.stderr.diff ================================================= --- syscall-restart2.stderr.exp 2012-10-23 03:55:37.379157691 +0200 +++ syscall-restart2.stderr.out 2012-10-23 04:01:21.259174801 +0200 @@ -1,3 +1,28 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: main (syscall-restart2.c:25) + + +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/none/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-23 03:55:37.379157691 +0200 +++ threaded-fork.stderr.out 2012-10-23 04:01:25.219174878 +0200 @@ -1,3 +1,28 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: main (threaded-fork.c:25) + + +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/drd/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-23 03:45:08.699127867 +0200 +++ threaded-fork.stderr.out 2012-10-23 03:55:28.349157170 +0200 @@ -1,6 +1,30 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:?) + by 0x........: vgPlain_assert_fail (m_libcassert.c:?) + by 0x........: handle_syscall (scheduler.c:?) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: main (threaded-fork.c:28) + + +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. + PASS ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/gdbserver_tests/mcclean_after_fork.stderr.diff ================================================= --- mcclean_after_fork.stderr.exp 2012-10-23 03:45:06.069127693 +0200 +++ mcclean_after_fork.stderr.out 2012-10-23 03:46:26.589132064 +0200 @@ -3,14 +3,26 @@ +valgrind: m_scheduler/scheduler.c:547 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... +sched status: + running_tid=1 -HEAP SUMMARY: - in use at exit: 0 bytes in 0 blocks - total heap usage: 0 allocs, 0 frees, 0 bytes allocated +Thread 1: status = VgTs_Runnable + ... -For a detailed leak analysis, rerun with: --leak-check=full -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 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. + Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-old/gdbserver_tests/mcclean_after_fork.stdoutB.diff ================================================= --- mcclean_after_fork.stdoutB.exp 2012-10-23 03:45:06.069127693 +0200 +++ mcclean_after_fork.stdoutB.out 2012-10-23 03:46:26.619132065 +0200 @@ -7,6 +7,6 @@ Hardware read watchpoint 4: mem Continuing. Hardware read watchpoint 4: mem -Value = 0 +Value = 256 main () at clean_after_fork.c:34 34 if (mem == 0) ================================================= ./valgrind-old/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-10-23 03:45:05.879127677 +0200 +++ tc18_semabuse.stderr.out 2012-10-23 03:52:00.589147617 +0200 @@ -21,7 +21,7 @@ ---------------------------------------------------------------- Thread #x's call to sem_post failed - with error code 22 (EINVAL: Invalid argument) + with error code 38 (ENOSYS: Function not implemented) at 0x........: sem_post_WRK (hg_intercepts.c:...) by 0x........: sem_post (hg_intercepts.c:...) by 0x........: main (tc18_semabuse.c:37) ================================================= ./valgrind-old/helgrind/tests/tc18_semabuse.stderr.diff-linux-mips32 ================================================= --- tc18_semabuse.stderr.exp-linux-mips32 2012-10-23 03:45:05.869127676 +0200 +++ tc18_semabuse.stderr.out 2012-10-23 03:52:00.589147617 +0200 @@ -18,5 +18,13 @@ by 0x........: sem_wait (hg_intercepts.c:...) by 0x........: main (tc18_semabuse.c:34) +---------------------------------------------------------------- -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) +Thread #x's call to sem_post failed + with error code 38 (ENOSYS: Function not implemented) + at 0x........: sem_post_WRK (hg_intercepts.c:...) + by 0x........: sem_post (hg_intercepts.c:...) + by 0x........: main (tc18_semabuse.c:37) + + +ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/helgrind/tests/tc20_verifywrap.stderr.diff ================================================= --- tc20_verifywrap.stderr.exp 2012-10-23 03:45:05.869127676 +0200 +++ tc20_verifywrap.stderr.out 2012-10-23 03:52:06.019147886 +0200 @@ -218,7 +218,7 @@ ---------------------------------------------------------------- Thread #x's call to sem_post failed - with error code 22 (EINVAL: Invalid argument) + with error code 38 (ENOSYS: Function not implemented) at 0x........: sem_post_WRK (hg_intercepts.c:...) by 0x........: sem_post (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:245) ================================================= ./valgrind-old/helgrind/tests/tc20_verifywrap.stderr.diff-mips32 ================================================= --- tc20_verifywrap.stderr.exp-mips32 2012-10-23 03:45:05.879127677 +0200 +++ tc20_verifywrap.stderr.out 2012-10-23 03:52:06.019147886 +0200 @@ -35,7 +35,7 @@ ---------------------------------------------------------------- Thread #x's call to pthread_join failed - with error code 45 (EDEADLK: Resource deadlock would occur) + with error code 35 (EDEADLK: Resource deadlock would occur) at 0x........: pthread_join_WRK (hg_intercepts.c:...) by 0x........: pthread_join (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:83) @@ -46,7 +46,7 @@ ---------------------------------------------------------------- Thread #x's call to pthread_mutex_init failed - with error code 122 (EOPNOTSUPP: Operation not supported on transport endpoint) + with error code 95 (EOPNOTSUPP: Operation not supported on transport endpoint) at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:92) @@ -215,6 +215,14 @@ by 0x........: sem_wait (hg_intercepts.c:...) by 0x........: main (tc20_verifywrap.c:242) +---------------------------------------------------------------- + +Thread #x's call to sem_post failed + with error code 38 (ENOSYS: Function not implemented) + at 0x........: sem_post_WRK (hg_intercepts.c:...) + by 0x........: sem_post (hg_intercepts.c:...) + by 0x........: main (tc20_verifywrap.c:245) + FIXME: can't figure out how to verify wrap of sem_post @@ -227,4 +235,4 @@ ... -ERROR SUMMARY: 22 errors from 22 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 23 errors from 23 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/memcheck/tests/addressable.stderr.diff ================================================= --- addressable.stderr.exp 2012-10-23 03:45:06.549127728 +0200 +++ addressable.stderr.out 2012-10-23 03:47:13.739133352 +0200 @@ -8,78 +8,101 @@ For counts of detected and suppressed errors, rerun with: -v ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -Unaddressable byte(s) found during client check request - at 0x........: test2 (addressable.c:48) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd - -Invalid write of size 1 - at 0x........: test2 (addressable.c:51) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd - - -Process terminating with default action of signal N (SIGSEGV or SIGBUS) - Bad memory (SIGSEGV or SIGBUS) at address 0x........ - at 0x........: test2 (addressable.c:51) - by 0x........: main (addressable.c:125) - If you believe this happened as a result of a stack - overflow in your program's main thread (unlikely but - possible), you can try to increase the size of the - main thread stack using the --main-stacksize= flag. - The main thread stack size used in this run was .... -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated +valgrind: m_scheduler/scheduler.c:547 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... -For a detailed leak analysis, rerun with: --leak-check=full +sched status: + running_tid=1 -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) +Thread 1: status = VgTs_Runnable + ... -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated -For a detailed leak analysis, rerun with: --leak-check=full +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. -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +If that doesn't help, please report this bug to: www.valgrind.org -Process terminating with default action of signal N (SIGSEGV or SIGBUS) - Bad memory (SIGSEGV or SIGBUS) at address 0x........ - at 0x........: test4 (addressable.c:74) - by 0x........: main (addressable.c:125) +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated -For a detailed leak analysis, rerun with: --leak-check=full +valgrind: m_scheduler/scheduler.c:547 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... -For counts of detected and suppressed errors, rerun with: -v -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -Uninitialised byte(s) found during client check request - at 0x........: test5 (addressable.c:85) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd - -Uninitialised byte(s) found during client check request - at 0x........: test5 (addressable.c:91) - by 0x........: main (addressable.c:125) - Address 0x........ is not stack'd, malloc'd or (recently) free'd +sched status: + running_tid=1 +Thread 1: status = VgTs_WaitSys + ... + by 0x........: main (addressable.c:119) -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated -For a detailed leak analysis, rerun with: --leak-check=full +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 ================================================= ./valgrind-old/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-10-23 03:45:06.669127737 +0200 +++ addressable.stdout.out 2012-10-23 03:47:13.699133349 +0200 @@ -1,5 +1,5 @@ Test 1: PASS -Test 2: PASS -Test 3: PASS -Test 4: PASS -Test 5: PASS +Test 2: exited with unexpected status 1 +Test 3: exited with unexpected status 1 +Test 4: exited with unexpected status 1 +Test 5: exited with unexpected status 1 ================================================= ./valgrind-old/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2012-10-23 03:45:06.129127697 +0200 +++ vbit-test.stderr.out 2012-10-23 03:49:18.889139872 +0200 @@ -0,0 +1,275 @@ + +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + ... + +sched status: + running_tid=0 + +Thread 1: status = VgTs_Runnable + ... + by 0x........: get_irop (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + by 0x........: main (in /home/cborntra/valgrind-nightly/valgrind-old/memcheck/tests/vbit-test/vbit-test) + + +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 + ================================================= ./valgrind-old/none/tests/allexec32.stderr.diff ================================================= --- allexec32.stderr.exp 2012-10-23 03:45:08.399127847 +0200 +++ allexec32.stderr.out 2012-10-23 03:49:48.219141421 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) +sched status: + running_tid=1 +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:40) +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:24) + by 0x........: main (allexec.c:40) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:22) + by 0x........: main (allexec.c:42) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:42) + ================================================= ./valgrind-old/none/tests/allexec32.stdout.diff ================================================= --- allexec32.stdout.exp 2012-10-23 03:45:08.419127848 +0200 +++ allexec32.stdout.out 2012-10-23 03:49:48.199141420 +0200 @@ -1,14 +1,9 @@ ./allexec32 will exec ./allexec32 program exec-ed: ./allexec32 child exited -program exec-ed: ./allexec32 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec32 child exited ./allexec32 will exec ./allexec64 -program exec-ed: ./allexec64 child exited -program exec-ed: ./allexec64 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec64 child exited ================================================= ./valgrind-old/none/tests/allexec64.stderr.diff ================================================= --- allexec64.stderr.exp 2012-10-23 03:45:08.439127849 +0200 +++ allexec64.stderr.out 2012-10-23 03:49:48.619141444 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) +sched status: + running_tid=1 +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:40) +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: test_allexec (allexec.c:24) + by 0x........: main (allexec.c:40) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:22) + by 0x........: main (allexec.c:42) + + +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: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) + by 0x........: main (allexec.c:42) + ================================================= ./valgrind-old/none/tests/allexec64.stdout.diff ================================================= --- allexec64.stdout.exp 2012-10-23 03:45:08.459127850 +0200 +++ allexec64.stdout.out 2012-10-23 03:49:48.589141443 +0200 @@ -1,14 +1,9 @@ ./allexec64 will exec ./allexec32 program exec-ed: ./allexec32 child exited -program exec-ed: ./allexec32 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec32 child exited ./allexec64 will exec ./allexec64 -program exec-ed: ./allexec64 child exited -program exec-ed: ./allexec64 constant_arg1 constant_arg2 child exited -program exec-ed: ./allexec64 child exited ================================================= ./valgrind-old/none/tests/async-sigs.stderr.diff ================================================= --- async-sigs.stderr.exp 2012-10-23 03:45:08.419127848 +0200 +++ async-sigs.stderr.out 2012-10-23 03:49:49.619141505 +0200 @@ -1,8 +1,30 @@ -testing: blocking=0 caught=11 fatal=7... PASSED -testing: blocking=0 caught=11 fatal=1... PASSED -testing: blocking=0 caught=10 fatal=7... PASSED -testing: blocking=0 caught=10 fatal=1... PASSED -testing: blocking=1 caught=11 fatal=7... PASSED -testing: blocking=1 caught=11 fatal=1... PASSED -testing: blocking=1 caught=10 fatal=7... PASSED -testing: blocking=1 caught=10 fatal=1... PASSED +testing: blocking=0 caught=11 fatal=7... +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_kill (async-sigs.c:53) + by 0x........: test (async-sigs.c:105) + by 0x........: main (async-sigs.c:129) + + +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. + +kill 26532 failed status=exit 1 ================================================= ./valgrind-old/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-10-23 03:45:08.419127848 +0200 +++ async-sigs.stderr.out 2012-10-23 03:49:49.619141505 +0200 @@ -1,8 +1,30 @@ -testing: blocking=0 caught=11 fatal=10... PASSED -testing: blocking=0 caught=11 fatal=1... PASSED -testing: blocking=0 caught=16 fatal=10... PASSED -testing: blocking=0 caught=16 fatal=1... PASSED -testing: blocking=1 caught=11 fatal=10... PASSED -testing: blocking=1 caught=11 fatal=1... PASSED -testing: blocking=1 caught=16 fatal=10... PASSED -testing: blocking=1 caught=16 fatal=1... PASSED +testing: blocking=0 caught=11 fatal=7... +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_kill (async-sigs.c:53) + by 0x........: test (async-sigs.c:105) + by 0x........: main (async-sigs.c:129) + + +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. + +kill 26532 failed status=exit 1 ================================================= ./valgrind-old/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-10-23 03:45:08.459127850 +0200 +++ exec-sigmask.stderr.out 2012-10-23 03:49:51.669141619 +0200 @@ -1,2 +1,31 @@ +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: vgPlain_client_syscall (syswrap-main.c:1633) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + by 0x........: do_exec (exec-sigmask.c:15) + by 0x........: main (exec-sigmask.c:51) + + +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. + +child exec failed + ================================================= ./valgrind-old/none/tests/pth_atfork1.stderr.diff ================================================= --- pth_atfork1.stderr.exp 2012-10-23 03:45:08.399127847 +0200 +++ pth_atfork1.stderr.out 2012-10-23 03:50:07.299142422 +0200 @@ -1,3 +1,31 @@ +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=2 + +Thread 2: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: thread (pth_atfork1.c:101) + by 0x........: start_thread (in /lib64/libpthread-2.14.1.so) + by 0x........: ??? (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. + +./pth_atfork1: pthread_join res != 0 ================================================= ./valgrind-old/none/tests/pth_atfork1.stdout.diff ================================================= --- pth_atfork1.stdout.exp 2012-10-23 03:45:08.419127848 +0200 +++ pth_atfork1.stdout.out 2012-10-23 03:50:07.079142410 +0200 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-old/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-10-23 03:45:08.419127848 +0200 +++ shell.stderr.out 2012-10-23 03:50:44.889144384 +0200 @@ -1,8 +1,253 @@ ./shell: ./x86/: is a directory -./shell: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell: ./shell_binaryfile: cannot execute binary file -./shell: ./shell_nosuchfile: No such file or directory -./shell: shell_nosuchfile: command not found + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/shell.stderr.diff-dash ================================================= --- shell.stderr.exp-dash 2012-10-23 03:45:08.399127847 +0200 +++ shell.stderr.out 2012-10-23 03:50:44.889144384 +0200 @@ -1,8 +1,253 @@ -./shell: 10: ./x86/: Permission denied -./shell: 13: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell_binaryfile: 4: Syntax error: ")" unexpected -./shell: 22: ./shell_nosuchfile: not found -./shell: 25: shell_nosuchfile: not found +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/shell.stderr.diff-dash2 ================================================= --- shell.stderr.exp-dash2 2012-10-23 03:45:08.419127848 +0200 +++ shell.stderr.out 2012-10-23 03:50:44.889144384 +0200 @@ -1,8 +1,253 @@ -./shell: 10: ./shell: ./x86/: Permission denied -./shell: 13: ./shell: ./shell.vgtest: Permission denied -execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2 -EXEC FAILED: I can't recover from execve() failing, so I'm dying. -Add more stringent tests in PRE(sys_execve), or work out how to recover. -./shell_binaryfile: 4: ./shell_binaryfile: Syntax error: ")" unexpected -./shell: 22: ./shell: ./shell_nosuchfile: not found -./shell: 25: ./shell: shell_nosuchfile: not found +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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: m_scheduler/scheduler.c:1060 (handle_syscall): Assertion '_qq_tst->sched_jmpbuf_valid' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: handle_syscall (scheduler.c:1060) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: bgp_delete (in /bin/bash) + by 0x........: make_child (in /bin/bash) + by 0x........: execute_command_internal (in /bin/bash) + by 0x........: execute_command (in /bin/bash) + by 0x........: reader_loop (in /bin/bash) + by 0x........: main (in /bin/bash) + + +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/none/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-23 03:45:08.459127850 +0200 +++ threaded-fork.stderr.out 2012-10-23 03:50:56.069144681 +0200 @@ -1,3 +1,33 @@ +Process terminating with default action of signal 4 (SIGILL) + Illegal opcode at address 0x........ + at 0x........: fork (in /...libc...) + by 0x........: main (threaded-fork.c:25) + +valgrind: m_scheduler/scheduler.c:947 (run_thread_for_a_while): Assertion 'done_this_time >= 0' failed. + at 0x........: report_and_quit (m_libcassert.c:235) + by 0x........: vgPlain_assert_fail (m_libcassert.c:309) + by 0x........: run_thread_for_a_while (scheduler.c:947) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + by 0x........: main (threaded-fork.c:25) + + +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. +