================================================= ./valgrind-new/drd/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-20 03:55:37.007616973 +0200 +++ threaded-fork.stderr.out 2012-10-20 04:05:53.297646666 +0200 @@ -1,6 +1,31 @@ -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........: _IO_list_unlock (in /...libc...) + by 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/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-10-20 03:55:33.657616772 +0200 +++ tc18_semabuse.stderr.out 2012-10-20 04:02:27.597637192 +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-20 03:55:33.657616772 +0200 +++ tc18_semabuse.stderr.out 2012-10-20 04:02:27.597637192 +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-20 03:55:33.657616772 +0200 +++ tc20_verifywrap.stderr.out 2012-10-20 04:02:32.927637460 +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-20 03:55:33.657616772 +0200 +++ tc20_verifywrap.stderr.out 2012-10-20 04:02:32.927637460 +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-20 03:55:34.787616836 +0200 +++ addressable.stderr.out 2012-10-20 03:57:41.877622668 +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-new/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-10-20 03:55:34.827616838 +0200 +++ addressable.stdout.out 2012-10-20 03:57:41.827622664 +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-new/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2012-10-20 03:55:33.997616791 +0200 +++ vbit-test.stderr.out 2012-10-20 03:59:46.917629437 +0200 @@ -0,0 +1,265 @@ + +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_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_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_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-new/none/tests/allexec32.stderr.diff ================================================= --- allexec32.stderr.exp 2012-10-20 03:55:36.707616954 +0200 +++ allexec32.stderr.out 2012-10-20 04:00:16.247631082 +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-20 03:55:36.727616955 +0200 +++ allexec32.stdout.out 2012-10-20 04:00:16.247631082 +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-20 03:55:36.757616957 +0200 +++ allexec64.stderr.out 2012-10-20 04:00:16.657631108 +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-20 03:55:36.767616958 +0200 +++ allexec64.stdout.out 2012-10-20 04:00:16.627631106 +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-20 03:55:36.727616955 +0200 +++ async-sigs.stderr.out 2012-10-20 04:00:17.907631187 +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:103) + 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 27456 failed status=exit 1 ================================================= ./valgrind-new/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-10-20 03:55:36.727616955 +0200 +++ async-sigs.stderr.out 2012-10-20 04:00:17.907631187 +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:103) + 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 27456 failed status=exit 1 ================================================= ./valgrind-new/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-10-20 03:55:36.767616958 +0200 +++ exec-sigmask.stderr.out 2012-10-20 04:00:20.067631309 +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-20 03:55:36.707616954 +0200 +++ pth_atfork1.stderr.out 2012-10-20 04:00:35.797632125 +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-20 03:55:36.727616955 +0200 +++ pth_atfork1.stdout.out 2012-10-20 04:00:35.597632110 +0200 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-new/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-10-20 03:55:36.727616955 +0200 +++ shell.stderr.out 2012-10-20 04:01:13.737634068 +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-20 03:55:36.707616954 +0200 +++ shell.stderr.out 2012-10-20 04:01:13.737634068 +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-20 03:55:36.727616955 +0200 +++ shell.stderr.out 2012-10-20 04:01:13.737634068 +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/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-20 03:55:36.767616958 +0200 +++ threaded-fork.stderr.out 2012-10-20 04:01:24.907634367 +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/cachegrind/tests/chdir.stderr.diff ================================================= --- chdir.stderr.exp 2012-10-20 03:45:08.227586541 +0200 +++ chdir.stderr.out 2012-10-20 03:49:27.607599449 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. I refs: I1 misses: ================================================= ./valgrind-old/cachegrind/tests/clreq.stderr.diff ================================================= --- clreq.stderr.exp 2012-10-20 03:45:08.227586541 +0200 +++ clreq.stderr.out 2012-10-20 03:49:27.857599466 +0200 @@ -0,0 +1 @@ +warning: L2 cache not installed, ignore LL results. ================================================= ./valgrind-old/cachegrind/tests/dlclose.stderr.diff ================================================= --- dlclose.stderr.exp 2012-10-20 03:45:08.227586541 +0200 +++ dlclose.stderr.out 2012-10-20 03:49:28.177599491 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. I refs: I1 misses: ================================================= ./valgrind-old/cachegrind/tests/notpower2.stderr.diff ================================================= --- notpower2.stderr.exp 2012-10-20 03:45:08.227586541 +0200 +++ notpower2.stderr.out 2012-10-20 03:49:28.437599511 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. I refs: I1 misses: ================================================= ./valgrind-old/cachegrind/tests/wrap5.stderr.diff ================================================= --- wrap5.stderr.exp 2012-10-20 03:45:08.227586541 +0200 +++ wrap5.stderr.out 2012-10-20 03:49:28.727599534 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. I refs: I1 misses: ================================================= ./valgrind-old/callgrind/tests/notpower2-hwpref.stderr.diff ================================================= --- notpower2-hwpref.stderr.exp 2012-10-20 03:45:06.437586444 +0200 +++ notpower2-hwpref.stderr.out 2012-10-20 03:49:29.217599567 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw Collected : ================================================= ./valgrind-old/callgrind/tests/notpower2-use.stderr.diff ================================================= --- notpower2-use.stderr.exp 2012-10-20 03:45:06.437586444 +0200 +++ notpower2-use.stderr.out 2012-10-20 03:49:29.477599585 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw AcCost1 SpLoss1 AcCost2 SpLoss2 Collected : ================================================= ./valgrind-old/callgrind/tests/notpower2-wb.stderr.diff ================================================= --- notpower2-wb.stderr.exp 2012-10-20 03:45:06.447586445 +0200 +++ notpower2-wb.stderr.out 2012-10-20 03:49:29.727599599 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw ILdmr DLdmr DLdmw Collected : ================================================= ./valgrind-old/callgrind/tests/notpower2.stderr.diff ================================================= --- notpower2.stderr.exp 2012-10-20 03:45:06.437586444 +0200 +++ notpower2.stderr.out 2012-10-20 03:49:29.977599612 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw Collected : ================================================= ./valgrind-old/callgrind/tests/simwork-both.stderr.diff ================================================= --- simwork-both.stderr.exp 2012-10-20 03:45:06.437586444 +0200 +++ simwork-both.stderr.out 2012-10-20 03:49:31.127599669 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw Bc Bcm Bi Bim Collected : ================================================= ./valgrind-old/callgrind/tests/simwork-cache.stderr.diff ================================================= --- simwork-cache.stderr.exp 2012-10-20 03:45:06.447586445 +0200 +++ simwork-cache.stderr.out 2012-10-20 03:49:32.527599754 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw Collected : ================================================= ./valgrind-old/callgrind/tests/simwork1.stderr.diff ================================================= --- simwork1.stderr.exp 2012-10-20 03:45:06.447586445 +0200 +++ simwork1.stderr.out 2012-10-20 03:49:33.707599826 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw Collected : ================================================= ./valgrind-old/callgrind/tests/simwork2.stderr.diff ================================================= --- simwork2.stderr.exp 2012-10-20 03:45:06.447586445 +0200 +++ simwork2.stderr.out 2012-10-20 03:49:34.927599899 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw ILdmr DLdmr DLdmw Collected : ================================================= ./valgrind-old/callgrind/tests/simwork3.stderr.diff ================================================= --- simwork3.stderr.exp 2012-10-20 03:45:06.447586445 +0200 +++ simwork3.stderr.out 2012-10-20 03:49:36.017599954 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw AcCost1 SpLoss1 AcCost2 SpLoss2 Collected : ================================================= ./valgrind-old/callgrind/tests/threads-use.stderr.diff ================================================= --- threads-use.stderr.exp 2012-10-20 03:45:06.437586444 +0200 +++ threads-use.stderr.out 2012-10-20 03:49:39.557600109 +0200 @@ -1,4 +1,5 @@ +warning: L2 cache not installed, ignore LL results. Events : Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw AcCost1 SpLoss1 AcCost2 SpLoss2 Ge sysCount sysTime Collected : ================================================= ./valgrind-old/drd/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-10-20 03:45:10.507586677 +0200 +++ threaded-fork.stderr.out 2012-10-20 03:55:27.017616396 +0200 @@ -1,6 +1,30 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_scheduler/scheduler.c:1058 (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/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-10-20 03:45:06.337586439 +0200 +++ tc18_semabuse.stderr.out 2012-10-20 03:52:00.247606827 +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-20 03:45:06.337586439 +0200 +++ tc18_semabuse.stderr.out 2012-10-20 03:52:00.247606827 +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-20 03:45:06.337586439 +0200 +++ tc20_verifywrap.stderr.out 2012-10-20 03:52:05.607607093 +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-20 03:45:06.337586439 +0200 +++ tc20_verifywrap.stderr.out 2012-10-20 03:52:05.607607093 +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-20 03:45:07.727586508 +0200 +++ addressable.stderr.out 2012-10-20 03:47:15.777592357 +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=1 -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_Yielding + ... + 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=1 + +Thread 1: status = VgTs_Yielding + ... + 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=1 + +Thread 1: status = VgTs_Yielding + ... + 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-old/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-10-20 03:45:07.787586512 +0200 +++ addressable.stdout.out 2012-10-20 03:47:15.727592353 +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-old/memcheck/tests/vbit-test/vbit-test.stderr.diff ================================================= --- vbit-test.stderr.exp 2012-10-20 03:45:06.627586457 +0200 +++ vbit-test.stderr.out 2012-10-20 03:49:20.137598955 +0200 @@ -0,0 +1,265 @@ + +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_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_scheduler/scheduler.c:545 (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_scheduler/scheduler.c:545 (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-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=1 + +Thread 1: status = VgTs_Yielding + ... + 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-old/none/tests/allexec32.stderr.diff ================================================= --- allexec32.stderr.exp 2012-10-20 03:45:10.207586659 +0200 +++ allexec32.stderr.out 2012-10-20 03:49:49.427600662 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1058 (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:1058) +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:1058 (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:1058) + +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:1058) + +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:1058) + +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-20 03:45:10.207586659 +0200 +++ allexec32.stdout.out 2012-10-20 03:49:49.397600660 +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-20 03:45:10.227586660 +0200 +++ allexec64.stderr.out 2012-10-20 03:49:49.817600687 +0200 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1058 (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:1058) +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:1058 (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:1058) + +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:1058) + +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:1058) + +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-20 03:45:10.247586661 +0200 +++ allexec64.stdout.out 2012-10-20 03:49:49.797600686 +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-20 03:45:10.207586659 +0200 +++ async-sigs.stderr.out 2012-10-20 03:49:50.837600751 +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:1058) + +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:106) + 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 29566 failed status=exit 1 ================================================= ./valgrind-old/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-10-20 03:45:10.207586659 +0200 +++ async-sigs.stderr.out 2012-10-20 03:49:50.837600751 +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:1058) + +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:106) + 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 29566 failed status=exit 1 ================================================= ./valgrind-old/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-10-20 03:45:10.247586661 +0200 +++ exec-sigmask.stderr.out 2012-10-20 03:49:52.917600878 +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:1058) + +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-20 03:45:10.187586658 +0200 +++ pth_atfork1.stderr.out 2012-10-20 03:50:08.577601771 +0200 @@ -1,3 +1,31 @@ +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +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-20 03:45:10.207586659 +0200 +++ pth_atfork1.stdout.out 2012-10-20 03:50:08.357601756 +0200 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-old/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-10-20 03:45:10.207586659 +0200 +++ shell.stderr.out 2012-10-20 03:50:46.527603698 +0200 @@ -1,8 +1,202 @@ ./shell: ./x86/: is a directory -./shell: ./shell.vgtest: Permission denied + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +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. + 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_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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + 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. + + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + 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:842 (run_thread_for_a_while): Assertion 'VG_(stats__n_xindirs_32) == 0' failed. + at 0x........: report_and_quit (m_libcassert.c:235) ================================================= ./valgrind-old/none/tests/shell.stderr.diff-dash ================================================= --- shell.stderr.exp-dash 2012-10-20 03:45:10.207586659 +0200 +++ shell.stderr.out 2012-10-20 03:50:46.527603698 +0200 @@ -1,8 +1,202 @@ -./shell: 10: ./x86/: Permission denied -./shell: 13: ./shell.vgtest: Permission denied +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +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. + 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: ./shell_binaryfile: cannot execute binary file + +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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + 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. + + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + 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-20 03:45:10.207586659 +0200 +++ shell.stderr.out 2012-10-20 03:50:46.527603698 +0200 @@ -1,8 +1,202 @@ -./shell: 10: ./shell: ./x86/: Permission denied -./shell: 13: ./shell: ./shell.vgtest: Permission denied +./shell: ./x86/: is a directory + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +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. + 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: ./shell_binaryfile: cannot execute binary file + +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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: waitpid (in /...libc...) + 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. + + +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: fork (in /...libc...) + 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-20 03:45:10.247586661 +0200 +++ threaded-fork.stderr.out 2012-10-20 03:50:57.687603986 +0200 @@ -1,3 +1,28 @@ +valgrind: m_scheduler/scheduler.c:1058 (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:1058) + +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. +