================================================= ./valgrind-new/drd/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-12-02 03:55:20.000942765 +0100 +++ threaded-fork.stderr.out 2012-12-02 04:05:21.320990075 +0100 @@ -1,6 +1,31 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_scheduler/scheduler.c:1061 (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/gdbserver_tests/mcbreak.stderrB.diff ================================================= --- mcbreak.stderrB.exp 2012-12-02 03:55:17.360942523 +0100 +++ mcbreak.stderrB.out 2012-12-02 03:56:37.200949979 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + vgdb-error value changed from 999999 to 0 n_errs_found 1 n_errs_shown 1 (vgdb-error 0) vgdb-error value changed from 0 to 0 ================================================= ./valgrind-new/gdbserver_tests/mcclean_after_fork.stderr.diff ================================================= --- mcclean_after_fork.stderr.exp 2012-12-02 03:55:17.360942523 +0100 +++ mcclean_after_fork.stderr.out 2012-12-02 03:56:38.670950037 +0100 @@ -2,15 +2,4 @@ (action at startup) vgdb me ... - - - -HEAP SUMMARY: - in use at exit: 0 bytes in 0 blocks - total heap usage: 0 allocs, 0 frees, 0 bytes allocated - -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) Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-new/gdbserver_tests/mcclean_after_fork.stderrB.diff ================================================= --- mcclean_after_fork.stderrB.exp 2012-12-02 03:55:17.360942523 +0100 +++ mcclean_after_fork.stderrB.out 2012-12-02 03:56:38.810950047 +0100 @@ -1,4 +1,10 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + monitor command request to kill this process Remote connection closed ================================================= ./valgrind-new/gdbserver_tests/mcclean_after_fork.stdoutB.diff ================================================= --- mcclean_after_fork.stdoutB.exp 2012-12-02 03:55:17.360942523 +0100 +++ mcclean_after_fork.stdoutB.out 2012-12-02 03:56:38.790950045 +0100 @@ -7,6 +7,6 @@ Hardware read watchpoint 4: mem Continuing. Hardware read watchpoint 4: mem -Value = 0 +Value = 11 main () at clean_after_fork.c:34 34 if (mem == 0) ================================================= ./valgrind-new/gdbserver_tests/mcleak.stderrB.diff ================================================= --- mcleak.stderrB.exp 2012-12-02 03:55:17.360942523 +0100 +++ mcleak.stderrB.out 2012-12-02 03:56:58.730950922 +0100 @@ -1,5 +1,9 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + 10 bytes in 1 blocks are still reachable in loss record ... of ... at 0x........: malloc (vg_replace_malloc.c:...) by 0x........: f (leak-delta.c:14) ================================================= ./valgrind-new/gdbserver_tests/mcmain_pic.stderrB.diff ================================================= --- mcmain_pic.stderrB.exp 2012-12-02 03:55:17.370942524 +0100 +++ mcmain_pic.stderrB.out 2012-12-02 03:57:00.260950987 +0100 @@ -1,2 +1,8 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + ================================================= ./valgrind-new/gdbserver_tests/mcvabits.stderrB.diff ================================================= --- mcvabits.stderrB.exp 2012-12-02 03:55:17.370942524 +0100 +++ mcvabits.stderrB.out 2012-12-02 03:57:05.100951215 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + Address 0x........ len 10 addressable Address 0x........ is 0 bytes inside data symbol "undefined" Address 0x........ len 10 defined ================================================= ./valgrind-new/gdbserver_tests/mssnapshot.stderrB.diff ================================================= --- mssnapshot.stderrB.exp 2012-12-02 03:55:17.370942524 +0100 +++ mssnapshot.stderrB.out 2012-12-02 03:57:07.970951360 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + general valgrind monitor commands: help [debug] : monitor command help. With debug: + debugging commands v.wait [] : sleep (default 0) then continue ================================================= ./valgrind-new/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-12-02 03:55:17.130942500 +0100 +++ tc18_semabuse.stderr.out 2012-12-02 04:02:07.610975684 +0100 @@ -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-12-02 03:55:17.120942499 +0100 +++ tc18_semabuse.stderr.out 2012-12-02 04:02:07.610975684 +0100 @@ -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-12-02 03:55:17.120942499 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 04:02:13.020976123 +0100 @@ -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-12-02 03:55:17.130942500 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 04:02:13.020976123 +0100 @@ -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/helgrind/tests/tc20_verifywrap.stderr.diff-s390x ================================================= --- tc20_verifywrap.stderr.exp-s390x 2012-12-02 03:55:17.140942501 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 04:02:13.020976123 +0100 @@ -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-12-02 03:55:17.860942568 +0100 +++ addressable.stderr.out 2012-12-02 03:57:25.140951918 +0100 @@ -8,49 +8,29 @@ 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:548 (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 + +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. -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 @@ -60,26 +40,54 @@ 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 +valgrind: m_scheduler/scheduler.c:548 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. + ... -HEAP SUMMARY: - in use at exit: ... bytes in ... blocks - total heap usage: ... allocs, ... frees, ... bytes allocated +sched status: + running_tid=0 -For a detailed leak analysis, rerun with: --leak-check=full +Thread 1: status = VgTs_WaitSys + ... + 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 ================================================= ./valgrind-new/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-12-02 03:55:17.910942572 +0100 +++ addressable.stdout.out 2012-12-02 03:57:25.080951913 +0100 @@ -1,5 +1,5 @@ Test 1: PASS -Test 2: PASS +Test 2: exited with unexpected status 1 Test 3: PASS -Test 4: PASS -Test 5: PASS +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-12-02 03:55:17.410942527 +0100 +++ vbit-test.stderr.out 2012-12-02 03:59:34.920963951 +0100 @@ -0,0 +1,265 @@ + +valgrind: m_scheduler/scheduler.c:548 (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:548 (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:548 (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:548 (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-12-02 03:55:19.680942735 +0100 +++ allexec32.stderr.out 2012-12-02 04:00:04.890966727 +0100 @@ -2,13 +2,141 @@ +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:1061) +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: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:1061 (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:1061) + +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:1061) + +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:1061) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) ================================================= ./valgrind-new/none/tests/allexec32.stdout.diff ================================================= --- allexec32.stdout.exp 2012-12-02 03:55:19.700942737 +0100 +++ allexec32.stdout.out 2012-12-02 04:00:04.870966725 +0100 @@ -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-12-02 03:55:19.720942739 +0100 +++ allexec64.stderr.out 2012-12-02 04:00:05.320966769 +0100 @@ -2,13 +2,139 @@ +valgrind: m_scheduler/scheduler.c:1061 (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:1061) +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:1061 (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:1061) + +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:1061) + +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:1061) + +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-12-02 03:55:19.730942740 +0100 +++ allexec64.stdout.out 2012-12-02 04:00:05.290966767 +0100 @@ -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-12-02 03:55:19.700942737 +0100 +++ async-sigs.stderr.out 2012-12-02 04:00:06.350966870 +0100 @@ -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:1061) + +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 48909 failed status=exit 1 ================================================= ./valgrind-new/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-12-02 03:55:19.700942737 +0100 +++ async-sigs.stderr.out 2012-12-02 04:00:06.350966870 +0100 @@ -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:1061) + +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 48909 failed status=exit 1 ================================================= ./valgrind-new/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-12-02 03:55:19.740942741 +0100 +++ exec-sigmask.stderr.out 2012-12-02 04:00:08.600967092 +0100 @@ -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:1061) + +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-12-02 03:55:19.680942735 +0100 +++ pth_atfork1.stderr.out 2012-12-02 04:00:24.930968626 +0100 @@ -1,3 +1,31 @@ +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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-12-02 03:55:19.690942736 +0100 +++ pth_atfork1.stdout.out 2012-12-02 04:00:24.690968602 +0100 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-new/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-12-02 03:55:19.690942736 +0100 +++ shell.stderr.out 2012-12-02 04:01:05.460971944 +0100 @@ -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:1061 (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:1061) + +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:1061 (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:1061) + +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:1061 (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:1061) + +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-12-02 03:55:19.680942735 +0100 +++ shell.stderr.out 2012-12-02 04:01:05.460971944 +0100 @@ -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:1061 (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:1061) + +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:1061 (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:1061) + +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:1061 (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:1061) + +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-12-02 03:55:19.690942736 +0100 +++ shell.stderr.out 2012-12-02 04:01:05.460971944 +0100 @@ -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:1061 (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:1061) + +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:1061 (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:1061) + +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:1061 (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:1061) + +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-12-02 03:55:19.730942740 +0100 +++ threaded-fork.stderr.out 2012-12-02 04:01:16.830972414 +0100 @@ -1,3 +1,29 @@ +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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: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-12-02 03:45:09.430894470 +0100 +++ threaded-fork.stderr.out 2012-12-02 03:55:10.280941843 +0100 @@ -1,6 +1,29 @@ -ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) +valgrind: m_scheduler/scheduler.c:1061 (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........: main (threaded-fork.c:39) + + +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/mcbreak.stderrB.diff ================================================= --- mcbreak.stderrB.exp 2012-12-02 03:45:07.000894245 +0100 +++ mcbreak.stderrB.out 2012-12-02 03:46:26.550901707 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + vgdb-error value changed from 999999 to 0 n_errs_found 1 n_errs_shown 1 (vgdb-error 0) vgdb-error value changed from 0 to 0 ================================================= ./valgrind-old/gdbserver_tests/mcclean_after_fork.stderr.diff ================================================= --- mcclean_after_fork.stderr.exp 2012-12-02 03:45:07.000894245 +0100 +++ mcclean_after_fork.stderr.out 2012-12-02 03:46:28.010901791 +0100 @@ -2,15 +2,4 @@ (action at startup) vgdb me ... - - - -HEAP SUMMARY: - in use at exit: 0 bytes in 0 blocks - total heap usage: 0 allocs, 0 frees, 0 bytes allocated - -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) Reset valgrind output to log (orderly_finish) ================================================= ./valgrind-old/gdbserver_tests/mcclean_after_fork.stderrB.diff ================================================= --- mcclean_after_fork.stderrB.exp 2012-12-02 03:45:07.000894245 +0100 +++ mcclean_after_fork.stderrB.out 2012-12-02 03:46:28.150901802 +0100 @@ -1,4 +1,10 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + monitor command request to kill this process Remote connection closed ================================================= ./valgrind-old/gdbserver_tests/mcclean_after_fork.stdoutB.diff ================================================= --- mcclean_after_fork.stdoutB.exp 2012-12-02 03:45:07.000894245 +0100 +++ mcclean_after_fork.stdoutB.out 2012-12-02 03:46:28.140901801 +0100 @@ -7,6 +7,6 @@ Hardware read watchpoint 4: mem Continuing. Hardware read watchpoint 4: mem -Value = 0 +Value = 11 main () at clean_after_fork.c:34 34 if (mem == 0) ================================================= ./valgrind-old/gdbserver_tests/mcleak.stderrB.diff ================================================= --- mcleak.stderrB.exp 2012-12-02 03:45:07.000894245 +0100 +++ mcleak.stderrB.out 2012-12-02 03:46:47.880902696 +0100 @@ -1,5 +1,9 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + 10 bytes in 1 blocks are still reachable in loss record ... of ... at 0x........: malloc (vg_replace_malloc.c:...) by 0x........: f (leak-delta.c:14) ================================================= ./valgrind-old/gdbserver_tests/mcmain_pic.stderrB.diff ================================================= --- mcmain_pic.stderrB.exp 2012-12-02 03:45:07.010894246 +0100 +++ mcmain_pic.stderrB.out 2012-12-02 03:46:49.400902759 +0100 @@ -1,2 +1,8 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + ================================================= ./valgrind-old/gdbserver_tests/mcvabits.stderrB.diff ================================================= --- mcvabits.stderrB.exp 2012-12-02 03:45:07.010894246 +0100 +++ mcvabits.stderrB.out 2012-12-02 03:46:54.530902993 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + Address 0x........ len 10 addressable Address 0x........ is 0 bytes inside data symbol "undefined" Address 0x........ len 10 defined ================================================= ./valgrind-old/gdbserver_tests/mssnapshot.stderrB.diff ================================================= --- mssnapshot.stderrB.exp 2012-12-02 03:45:07.010894246 +0100 +++ mssnapshot.stderrB.out 2012-12-02 03:46:57.400903101 +0100 @@ -1,5 +1,11 @@ relaying data between gdb and process .... + + vgdb-error value changed from 0 to 999999 + + + + general valgrind monitor commands: help [debug] : monitor command help. With debug: + debugging commands v.wait [] : sleep (default 0) then continue ================================================= ./valgrind-old/helgrind/tests/tc18_semabuse.stderr.diff ================================================= --- tc18_semabuse.stderr.exp 2012-12-02 03:45:06.800894228 +0100 +++ tc18_semabuse.stderr.out 2012-12-02 03:51:56.440927421 +0100 @@ -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-12-02 03:45:06.800894228 +0100 +++ tc18_semabuse.stderr.out 2012-12-02 03:51:56.440927421 +0100 @@ -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-12-02 03:45:06.800894228 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 03:52:01.840927857 +0100 @@ -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-12-02 03:45:06.800894228 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 03:52:01.840927857 +0100 @@ -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/helgrind/tests/tc20_verifywrap.stderr.diff-s390x ================================================= --- tc20_verifywrap.stderr.exp-s390x 2012-12-02 03:45:06.810894229 +0100 +++ tc20_verifywrap.stderr.out 2012-12-02 03:52:01.840927857 +0100 @@ -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-12-02 03:45:07.480894288 +0100 +++ addressable.stderr.out 2012-12-02 03:47:14.510903674 +0100 @@ -8,78 +8,102 @@ 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:548 (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_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 +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:548 (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=0 +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 ================================================= ./valgrind-old/memcheck/tests/addressable.stdout.diff ================================================= --- addressable.stdout.exp 2012-12-02 03:45:07.540894294 +0100 +++ addressable.stdout.out 2012-12-02 03:47:14.460903669 +0100 @@ -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-12-02 03:45:07.050894249 +0100 +++ vbit-test.stderr.out 2012-12-02 03:49:23.880915667 +0100 @@ -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:548 (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:548 (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_scheduler/scheduler.c:548 (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-old/none/tests/allexec32.stderr.diff ================================================= --- allexec32.stderr.exp 2012-12-02 03:45:09.120894441 +0100 +++ allexec32.stderr.out 2012-12-02 03:49:53.840918444 +0100 @@ -2,13 +2,141 @@ +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:1061) +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: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:1061 (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:1061) + +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:1061) + +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:1061) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) ================================================= ./valgrind-old/none/tests/allexec32.stdout.diff ================================================= --- allexec32.stdout.exp 2012-12-02 03:45:09.130894442 +0100 +++ allexec32.stdout.out 2012-12-02 03:49:53.820918442 +0100 @@ -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-12-02 03:45:09.160894444 +0100 +++ allexec64.stderr.out 2012-12-02 03:49:54.270918486 +0100 @@ -2,13 +2,141 @@ +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:1061) +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: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:1061 (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:1061) + +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:1061) + +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:1061) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_WaitSys + at 0x........: wait (in /...libc...) + by 0x........: test_allexec (allexec.c:23) ================================================= ./valgrind-old/none/tests/allexec64.stdout.diff ================================================= --- allexec64.stdout.exp 2012-12-02 03:45:09.170894445 +0100 +++ allexec64.stdout.out 2012-12-02 03:49:54.250918484 +0100 @@ -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-12-02 03:45:09.130894442 +0100 +++ async-sigs.stderr.out 2012-12-02 03:49:55.310918587 +0100 @@ -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:1061) + +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 50748 failed status=exit 1 ================================================= ./valgrind-old/none/tests/async-sigs.stderr.diff-mips32 ================================================= --- async-sigs.stderr.exp-mips32 2012-12-02 03:45:09.130894442 +0100 +++ async-sigs.stderr.out 2012-12-02 03:49:55.310918587 +0100 @@ -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:1061) + +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 50748 failed status=exit 1 ================================================= ./valgrind-old/none/tests/exec-sigmask.stderr.diff ================================================= --- exec-sigmask.stderr.exp 2012-12-02 03:45:09.180894446 +0100 +++ exec-sigmask.stderr.out 2012-12-02 03:49:57.590918813 +0100 @@ -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:1061) + +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-12-02 03:45:09.120894441 +0100 +++ pth_atfork1.stderr.out 2012-12-02 03:50:13.930920345 +0100 @@ -1,3 +1,31 @@ +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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-12-02 03:45:09.130894442 +0100 +++ pth_atfork1.stdout.out 2012-12-02 03:50:13.690920321 +0100 @@ -1 +0,0 @@ -all ok ================================================= ./valgrind-old/none/tests/shell.stderr.diff ================================================= --- shell.stderr.exp 2012-12-02 03:45:09.130894442 +0100 +++ shell.stderr.out 2012-12-02 03:50:54.430923670 +0100 @@ -1,8 +1,234 @@ ./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 + +Process terminating with default action of signal 11 (SIGSEGV) + Access not within mapped region at address 0x........ + at 0x........: hash_search (in /bin/bash) + by 0x........: ??? (in /...libc...) + 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 .... +./shell: 1275 Segmentation fault ./shell.vgtest + +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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:1061 (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:1061) + +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_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:1061) + +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 ================================================= ./valgrind-old/none/tests/shell.stderr.diff-dash ================================================= --- shell.stderr.exp-dash 2012-12-02 03:45:09.120894441 +0100 +++ shell.stderr.out 2012-12-02 03:50:54.430923670 +0100 @@ -1,8 +1,234 @@ -./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 + +Process terminating with default action of signal 11 (SIGSEGV) + Access not within mapped region at address 0x........ + at 0x........: hash_search (in /bin/bash) + by 0x........: ??? (in /...libc...) + 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 .... +./shell: 1275 Segmentation fault ./shell.vgtest + +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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:1061 (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:1061) + +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_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:1061) + +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. ================================================= ./valgrind-old/none/tests/shell.stderr.diff-dash2 ================================================= --- shell.stderr.exp-dash2 2012-12-02 03:45:09.130894442 +0100 +++ shell.stderr.out 2012-12-02 03:50:54.430923670 +0100 @@ -1,8 +1,234 @@ -./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 + +Process terminating with default action of signal 11 (SIGSEGV) + Access not within mapped region at address 0x........ + at 0x........: hash_search (in /bin/bash) + by 0x........: ??? (in /...libc...) + 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 .... +./shell: 1275 Segmentation fault ./shell.vgtest + +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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:1061 (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:1061) + +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_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:1061) + +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. ================================================= ./valgrind-old/none/tests/threaded-fork.stderr.diff ================================================= --- threaded-fork.stderr.exp 2012-12-02 03:45:09.170894445 +0100 +++ threaded-fork.stderr.out 2012-12-02 03:51:05.800924135 +0100 @@ -1,3 +1,28 @@ +valgrind: m_scheduler/scheduler.c:1061 (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:1061) + +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. +