================================================= ./valgrind-new/exp-ptrcheck/tests/ccc.stderr.diff-glibc25-amd64 ================================================= --- ccc.stderr.exp-glibc25-amd64 2009-07-05 03:26:33.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:47:52.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/exp-ptrcheck/tests/ccc.stderr.diff-glibc27-x86 ================================================= --- ccc.stderr.exp-glibc27-x86 2009-07-05 03:26:33.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:47:52.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:25) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/exp-ptrcheck/tests/ccc.stderr.diff-glibc28-amd64 ================================================= --- ccc.stderr.exp-glibc28-amd64 2009-07-05 03:26:33.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:47:52.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/exp-ptrcheck/tests/pth_create.stderr.diff ================================================= --- pth_create.stderr.exp 2009-07-05 03:26:33.000000000 +0100 +++ pth_create.stderr.out 2009-07-05 03:48:52.000000000 +0100 @@ -1,18 +1,31 @@ -Invalid write of size 4 +t9 = CASle(t27::t16->t15) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable at 0x........: pthread_key_create (in /...libpthread...) by 0x........: main (pth_create.c:17) - Address 0x........ is 1 bytes inside the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (pth_create.c:14) -Invalid write of size 4 - at 0x........: pthread_key_create (in /...libpthread...) - by 0x........: main (pth_create.c:19) - Address 0x........ is 0 bytes inside the accessing pointer's - once-legitimate range, a block of size 4 free'd - at 0x........: free (vg_replace_malloc.c:...) - by 0x........: main (pth_create.c:18) -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) +Note: see also the FAQ in the source distribution. +It contains workarounds to several common problems. +In particular, if Valgrind aborted or crashed after +identifying problems in your program, there's a good chance +that fixing those problems will prevent Valgrind aborting or +crashing, especially if it happened in m_mallocfree.c. + +If that doesn't help, please report this bug to: www.valgrind.org + +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. + ================================================= ./valgrind-new/exp-ptrcheck/tests/pth_specific.stderr.diff ================================================= --- pth_specific.stderr.exp 2009-07-05 03:26:33.000000000 +0100 +++ pth_specific.stderr.out 2009-07-05 03:48:57.000000000 +0100 @@ -5,12 +5,33 @@ legitimate range, a block of size 100 alloc'd at 0x........: malloc (vg_replace_malloc.c:...) by 0x........: main (pth_specific.c:17) +t9 = CASle(t27::t16->t15) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) -Invalid read of size 1 - at 0x........: main (pth_specific.c:27) - Address 0x........ is 1 bytes before the accessing pointer's - legitimate range, a block of size 100 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (pth_specific.c:17) +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: pthread_key_create (in /...libpthread...) + by 0x........: main (pth_specific.c:22) + + +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. -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/memcheck/tests/x86-linux/scalar.stderr.diff ================================================= --- scalar.stderr.exp 2009-07-05 03:26:34.000000000 +0100 +++ scalar.stderr.out 2009-07-05 03:37:32.000000000 +0100 @@ -10,6 +10,10 @@ ----------------------------------------------------- 3: __NR_read 1+3s 1m ----------------------------------------------------- +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param (syscallno) contains uninitialised byte(s) ... @@ -499,15 +503,15 @@ 55: __NR_fcntl (DUPFD) 1s 0m ----------------------------------------------------- +More than 100 errors detected. Subsequent errors +will still be recorded, but in less detail than before. + Syscall param fcntl(arg) contains uninitialised byte(s) ... ----------------------------------------------------- 55: __NR_fcntl (GETLK) 1s 0m ----------------------------------------------------- -More than 100 errors detected. Subsequent errors -will still be recorded, but in less detail than before. - Syscall param fcntl(lock) contains uninitialised byte(s) ... ----------------------------------------------------- ================================================= ./valgrind-new/memcheck/tests/x86-linux/scalar_exit_group.stderr.diff ================================================= --- scalar_exit_group.stderr.exp 2009-07-05 03:26:34.000000000 +0100 +++ scalar_exit_group.stderr.out 2009-07-05 03:37:33.000000000 +0100 @@ -1,5 +1,9 @@ ----------------------------------------------------- 252: __NR_exit_group 1s 0m ----------------------------------------------------- +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param exit_group(status) contains uninitialised byte(s) ... ================================================= ./valgrind-new/memcheck/tests/x86-linux/scalar_supp.stderr.diff ================================================= --- scalar_supp.stderr.exp 2009-07-05 03:26:34.000000000 +0100 +++ scalar_supp.stderr.out 2009-07-05 03:37:34.000000000 +0100 @@ -1,3 +1,7 @@ +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param (syscallno) contains uninitialised byte(s) ... ================================================= ./valgrind-new/none/tests/amd64/bug127521-64.stderr.diff ================================================= --- bug127521-64.stderr.exp 2009-07-05 03:26:39.000000000 +0100 +++ bug127521-64.stderr.out 2009-07-05 03:38:45.000000000 +0100 @@ -1,2 +1,20 @@ +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +valgrind: Unrecognised instruction at address 0x......... +Your program just tried to execute an instruction that Valgrind +did not recognise. There are two possible reasons for this. +1. Your program has a bug and erroneously jumped to a non-code + location. If you are running Memcheck and you just saw a + warning about a bad jump, it's probably your program's fault. +2. The instruction is legitimate but Valgrind doesn't handle it, + i.e. it's Valgrind's fault. If you think this is the case or + you are not sure, please let us know and we'll try to fix it. +Either way, Valgrind will now raise a SIGILL signal which will +probably kill your program. + +Process terminating with default action of signal 4 (SIGILL) + Illegal opcode at address 0x........ + at 0x........: do_cmpxchg16b (bug127521-64.c:79) + by 0x........: try16b (bug127521-64.c:106) + by 0x........: main (bug127521-64.c:135) ================================================= ./valgrind-new/none/tests/amd64/bug127521-64.stdout.diff ================================================= --- bug127521-64.stdout.exp 2009-07-05 03:26:39.000000000 +0100 +++ bug127521-64.stdout.out 2009-07-05 03:38:44.000000000 +0100 @@ -1,24 +0,0 @@ - Q d:a=0:1 mem=5:4 c:b=3:2 -> z=0 d:a=5:4 mem=5:4 - Q d:a=0:1 mem=0:1 c:b=3:2 -> z=1 d:a=0:1 mem=3:2 - Q d:a=0:1 mem=0:4 c:b=3:2 -> z=0 d:a=0:4 mem=0:4 - Q d:a=0:1 mem=0:0 c:b=3:2 -> z=0 d:a=0:0 mem=0:0 - Q d:a=0:1 mem=5:0 c:b=3:2 -> z=0 d:a=5:0 mem=5:0 - Q d:a=0:1 mem=1:1 c:b=3:2 -> z=0 d:a=1:1 mem=1:1 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=5:4 mem=5:4 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=1 d:a=deadbeef00000000:deadbeef00000001 mem=3:2 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=0:4 mem=0:4 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=0:0 mem=0:0 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=5:0 mem=5:0 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=1:1 mem=1:1 -QQ d:a=0:1 mem=5:4 c:b=3:2 -> z=0 d:a=5:4 mem=5:4 -QQ d:a=0:1 mem=0:1 c:b=3:2 -> z=1 d:a=0:1 mem=3:2 -QQ d:a=0:1 mem=0:4 c:b=3:2 -> z=0 d:a=0:4 mem=0:4 -QQ d:a=0:1 mem=0:0 c:b=3:2 -> z=0 d:a=0:0 mem=0:0 -QQ d:a=0:1 mem=5:0 c:b=3:2 -> z=0 d:a=5:0 mem=5:0 -QQ d:a=0:1 mem=1:1 c:b=3:2 -> z=0 d:a=1:1 mem=1:1 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000005:deadbeef00000004 mem=deadbeef00000005:deadbeef00000004 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=1 d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000003:deadbeef00000002 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000000:deadbeef00000004 mem=deadbeef00000000:deadbeef00000004 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000000:deadbeef00000000 mem=deadbeef00000000:deadbeef00000000 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000005:deadbeef00000000 mem=deadbeef00000005:deadbeef00000000 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000001:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001 ================================================= ./valgrind-old/exp-ptrcheck/tests/ccc.stderr.diff-glibc25-amd64 ================================================= --- ccc.stderr.exp-glibc25-amd64 2009-07-05 03:05:13.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:24:44.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/exp-ptrcheck/tests/ccc.stderr.diff-glibc27-x86 ================================================= --- ccc.stderr.exp-glibc27-x86 2009-07-05 03:05:13.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:24:44.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:25) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/exp-ptrcheck/tests/ccc.stderr.diff-glibc28-amd64 ================================================= --- ccc.stderr.exp-glibc28-amd64 2009-07-05 03:05:13.000000000 +0100 +++ ccc.stderr.out 2009-07-05 03:24:44.000000000 +0100 @@ -1,45 +1,38 @@ -Invalid read of size 4 - at 0x........: main (ccc.cpp:20) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:8) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:21) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: ...operator new... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:9) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 40 alloc'd - at 0x........: ...operator new[]... (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:10) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:23) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: calloc (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:11) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:24) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:12) - -Invalid read of size 4 - at 0x........: main (ccc.cpp:22) - Address 0x........ is 4 bytes before the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: memalign (vg_replace_malloc.c:...) - by 0x........: posix_memalign (vg_replace_malloc.c:...) - by 0x........: main (ccc.cpp:14) +t4 = CASle(t3::t0->t2) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: __gnu_cxx::__exchange_and_add(int volatile*, int) (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: std::ios_base::Init::Init() (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? (in /usr/lib64/libstdc++.so.6.0.8) + by 0x........: ??? + by 0x........: call_init (dl-init.c:70) + by 0x........: _dl_init (dl-init.c:134) + by 0x........: ??? (in /lib64/ld-2.6.so) + + +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. -ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/exp-ptrcheck/tests/pth_create.stderr.diff ================================================= --- pth_create.stderr.exp 2009-07-05 03:05:13.000000000 +0100 +++ pth_create.stderr.out 2009-07-05 03:25:48.000000000 +0100 @@ -1,18 +1,31 @@ -Invalid write of size 4 +t9 = CASle(t27::t16->t15) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable at 0x........: pthread_key_create (in /...libpthread...) by 0x........: main (pth_create.c:17) - Address 0x........ is 1 bytes inside the accessing pointer's - legitimate range, a block of size 4 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (pth_create.c:14) -Invalid write of size 4 - at 0x........: pthread_key_create (in /...libpthread...) - by 0x........: main (pth_create.c:19) - Address 0x........ is 0 bytes inside the accessing pointer's - once-legitimate range, a block of size 4 free'd - at 0x........: free (vg_replace_malloc.c:...) - by 0x........: main (pth_create.c:18) -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) +Note: see also the FAQ in the source distribution. +It contains workarounds to several common problems. +In particular, if Valgrind aborted or crashed after +identifying problems in your program, there's a good chance +that fixing those problems will prevent Valgrind aborting or +crashing, especially if it happened in m_mallocfree.c. + +If that doesn't help, please report this bug to: www.valgrind.org + +In the bug report, send all the above text, the valgrind +version, and what OS and version you are using. Thanks. + ================================================= ./valgrind-old/exp-ptrcheck/tests/pth_specific.stderr.diff ================================================= --- pth_specific.stderr.exp 2009-07-05 03:05:13.000000000 +0100 +++ pth_specific.stderr.out 2009-07-05 03:25:53.000000000 +0100 @@ -5,12 +5,33 @@ legitimate range, a block of size 100 alloc'd at 0x........: malloc (vg_replace_malloc.c:...) by 0x........: main (pth_specific.c:17) +t9 = CASle(t27::t16->t15) +exp-ptrcheck: h_main.c:4820 (schemeS): the 'impossible' happened. + at 0x........: report_and_quit (m_libcassert.c:145) + by 0x........: vgPlain_assert_fail (m_libcassert.c:216) + by 0x........: h_instrument (h_main.c:4820) + by 0x........: LibVEX_Translate (main_main.c:500) + by 0x........: vgPlain_translate (m_translate.c:1517) + by 0x........: vgPlain_scheduler (scheduler.c:844) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) -Invalid read of size 1 - at 0x........: main (pth_specific.c:27) - Address 0x........ is 1 bytes before the accessing pointer's - legitimate range, a block of size 100 alloc'd - at 0x........: malloc (vg_replace_malloc.c:...) - by 0x........: main (pth_specific.c:17) +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: pthread_key_create (in /...libpthread...) + by 0x........: main (pth_specific.c:22) + + +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. -ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/memcheck/tests/x86-linux/scalar.stderr.diff ================================================= --- scalar.stderr.exp 2009-07-05 03:05:15.000000000 +0100 +++ scalar.stderr.out 2009-07-05 03:16:11.000000000 +0100 @@ -10,6 +10,10 @@ ----------------------------------------------------- 3: __NR_read 1+3s 1m ----------------------------------------------------- +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param (syscallno) contains uninitialised byte(s) ... @@ -499,15 +503,15 @@ 55: __NR_fcntl (DUPFD) 1s 0m ----------------------------------------------------- +More than 100 errors detected. Subsequent errors +will still be recorded, but in less detail than before. + Syscall param fcntl(arg) contains uninitialised byte(s) ... ----------------------------------------------------- 55: __NR_fcntl (GETLK) 1s 0m ----------------------------------------------------- -More than 100 errors detected. Subsequent errors -will still be recorded, but in less detail than before. - Syscall param fcntl(lock) contains uninitialised byte(s) ... ----------------------------------------------------- ================================================= ./valgrind-old/memcheck/tests/x86-linux/scalar_exit_group.stderr.diff ================================================= --- scalar_exit_group.stderr.exp 2009-07-05 03:05:15.000000000 +0100 +++ scalar_exit_group.stderr.out 2009-07-05 03:16:12.000000000 +0100 @@ -1,5 +1,9 @@ ----------------------------------------------------- 252: __NR_exit_group 1s 0m ----------------------------------------------------- +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param exit_group(status) contains uninitialised byte(s) ... ================================================= ./valgrind-old/memcheck/tests/x86-linux/scalar_supp.stderr.diff ================================================= --- scalar_supp.stderr.exp 2009-07-05 03:05:15.000000000 +0100 +++ scalar_supp.stderr.out 2009-07-05 03:16:13.000000000 +0100 @@ -1,3 +1,7 @@ +Conditional jump or move depends on uninitialised value(s) + at 0x........: _dl_runtime_resolve (in /lib/ld-2.6.so) + by 0x........: (below main) + Syscall param (syscallno) contains uninitialised byte(s) ... ================================================= ./valgrind-old/none/tests/amd64/bug127521-64.stderr.diff ================================================= --- bug127521-64.stderr.exp 2009-07-05 03:05:21.000000000 +0100 +++ bug127521-64.stderr.out 2009-07-05 03:16:42.000000000 +0100 @@ -1,2 +1,20 @@ +vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ +valgrind: Unrecognised instruction at address 0x......... +Your program just tried to execute an instruction that Valgrind +did not recognise. There are two possible reasons for this. +1. Your program has a bug and erroneously jumped to a non-code + location. If you are running Memcheck and you just saw a + warning about a bad jump, it's probably your program's fault. +2. The instruction is legitimate but Valgrind doesn't handle it, + i.e. it's Valgrind's fault. If you think this is the case or + you are not sure, please let us know and we'll try to fix it. +Either way, Valgrind will now raise a SIGILL signal which will +probably kill your program. + +Process terminating with default action of signal 4 (SIGILL) + Illegal opcode at address 0x........ + at 0x........: do_cmpxchg16b (bug127521-64.c:79) + by 0x........: try16b (bug127521-64.c:106) + by 0x........: main (bug127521-64.c:135) ================================================= ./valgrind-old/none/tests/amd64/bug127521-64.stdout.diff ================================================= --- bug127521-64.stdout.exp 2009-07-05 03:05:21.000000000 +0100 +++ bug127521-64.stdout.out 2009-07-05 03:16:42.000000000 +0100 @@ -1,24 +0,0 @@ - Q d:a=0:1 mem=5:4 c:b=3:2 -> z=0 d:a=5:4 mem=5:4 - Q d:a=0:1 mem=0:1 c:b=3:2 -> z=1 d:a=0:1 mem=3:2 - Q d:a=0:1 mem=0:4 c:b=3:2 -> z=0 d:a=0:4 mem=0:4 - Q d:a=0:1 mem=0:0 c:b=3:2 -> z=0 d:a=0:0 mem=0:0 - Q d:a=0:1 mem=5:0 c:b=3:2 -> z=0 d:a=5:0 mem=5:0 - Q d:a=0:1 mem=1:1 c:b=3:2 -> z=0 d:a=1:1 mem=1:1 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=5:4 mem=5:4 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=1 d:a=deadbeef00000000:deadbeef00000001 mem=3:2 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=0:4 mem=0:4 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=0:0 mem=0:0 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=5:0 mem=5:0 - Q d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=1:1 mem=1:1 -QQ d:a=0:1 mem=5:4 c:b=3:2 -> z=0 d:a=5:4 mem=5:4 -QQ d:a=0:1 mem=0:1 c:b=3:2 -> z=1 d:a=0:1 mem=3:2 -QQ d:a=0:1 mem=0:4 c:b=3:2 -> z=0 d:a=0:4 mem=0:4 -QQ d:a=0:1 mem=0:0 c:b=3:2 -> z=0 d:a=0:0 mem=0:0 -QQ d:a=0:1 mem=5:0 c:b=3:2 -> z=0 d:a=5:0 mem=5:0 -QQ d:a=0:1 mem=1:1 c:b=3:2 -> z=0 d:a=1:1 mem=1:1 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000005:deadbeef00000004 mem=deadbeef00000005:deadbeef00000004 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=1 d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000003:deadbeef00000002 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000004 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000000:deadbeef00000004 mem=deadbeef00000000:deadbeef00000004 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000000:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000000:deadbeef00000000 mem=deadbeef00000000:deadbeef00000000 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000005:deadbeef00000000 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000005:deadbeef00000000 mem=deadbeef00000005:deadbeef00000000 -QQ d:a=deadbeef00000000:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001 c:b=deadbeef00000003:deadbeef00000002 -> z=0 d:a=deadbeef00000001:deadbeef00000001 mem=deadbeef00000001:deadbeef00000001