================================================= ./valgrind-new/helgrind/tests/pth_barrier3.stderr.diff ================================================= --- pth_barrier3.stderr.exp 2012-02-02 03:36:15.530962252 +0000 +++ pth_barrier3.stderr.out 2012-02-02 03:44:41.904963198 +0000 @@ -35,3 +35,843 @@ by 0x........: barriers_and_races (pth_barrier.c:76) by 0x........: main (pth_barrier.c:122) +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- ================================================= ./valgrind-new/memcheck/tests/bug287260.stderr.diff ================================================= --- bug287260.stderr.exp 2012-02-02 03:36:16.857935347 +0000 +++ bug287260.stderr.out 2012-02-02 03:40:41.991262116 +0000 @@ -1,4 +1,20 @@ +Use of uninitialised value of size 8 + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + 45 HEAP SUMMARY: @@ -8,4 +24,5 @@ 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) +Use --track-origins=yes to see where uninitialised values come from +ERROR SUMMARY: 6 errors from 4 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/memcheck/tests/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2012-02-02 03:36:16.825935997 +0000 +++ err_disable4.stderr.out 2012-02-02 03:40:47.362151461 +0000 @@ -1,6 +1,7 @@ -------- Letting 498 threads exit w/ errs disabled ------ +err_disable4: err_disable4.c:85: main: Assertion `!r' failed. WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. @@ -1114,399 +1115,3 @@ WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use ================================================= ./valgrind-new/memcheck/tests/linux/stack_switch.stderr.diff ================================================= --- stack_switch.stderr.exp 2012-02-02 03:36:16.629939970 +0000 +++ stack_switch.stderr.out 2012-02-02 03:41:03.275550027 +0000 @@ -0,0 +1,3 @@ +Syscall param clone(child_tidptr) contains uninitialised byte(s) + ... + ================================================= ./valgrind-old/helgrind/tests/pth_barrier3.stderr.diff ================================================= --- pth_barrier3.stderr.exp 2012-02-02 03:21:37.601454624 +0000 +++ pth_barrier3.stderr.out 2012-02-02 03:30:59.208450433 +0000 @@ -35,3 +35,843 @@ by 0x........: barriers_and_races (pth_barrier.c:76) by 0x........: main (pth_barrier.c:122) +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- + +Possible data race during write of size 1 at 0x........ by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +This conflicts with a previous write of size 1 by thread #x +Locks held: none + at 0x........: threadfunc (pth_barrier.c:60) + by 0x........: mythread_wrapper (hg_intercepts.c:...) + ... + +Address 0x........ is 0 bytes inside a block of size 1 alloc'd + at 0x........: malloc (vg_replace_malloc.c:...) + by 0x........: barriers_and_races (pth_barrier.c:76) + by 0x........: main (pth_barrier.c:122) + +---Thread-Announcement------------------------------------------ + +Thread #x was created + ... + by 0x........: pthread_create_WRK (hg_intercepts.c:...) + by 0x........: pthread_create@* (hg_intercepts.c:...) + by 0x........: barriers_and_races (pth_barrier.c:92) + by 0x........: main (pth_barrier.c:122) + +---------------------------------------------------------------- ================================================= ./valgrind-old/memcheck/tests/bug287260.stderr.diff ================================================= --- bug287260.stderr.exp 2012-02-02 03:21:39.125422655 +0000 +++ bug287260.stderr.out 2012-02-02 03:26:07.559271604 +0000 @@ -1,4 +1,20 @@ +Use of uninitialised value of size 8 + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + +Conditional jump or move depends on uninitialised value(s) + ... + by 0x........: main (bug287260.c:14) + 45 HEAP SUMMARY: @@ -8,4 +24,5 @@ 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) +Use --track-origins=yes to see where uninitialised values come from +ERROR SUMMARY: 6 errors from 4 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/memcheck/tests/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2012-02-02 03:21:39.105423075 +0000 +++ err_disable4.stderr.out 2012-02-02 03:26:13.000158878 +0000 @@ -1,6 +1,7 @@ -------- Letting 498 threads exit w/ errs disabled ------ +err_disable4: err_disable4.c:85: main: Assertion `!r' failed. WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. @@ -1135,378 +1136,3 @@ WARNING: exiting thread has error reporting disabled. WARNING: possibly as a result of some mistake in the use WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use -WARNING: of the VALGRIND_DISABLE_ERROR_REPORTING macros. -WARNING: exiting thread has error reporting disabled. -WARNING: possibly as a result of some mistake in the use ================================================= ./valgrind-old/memcheck/tests/linux/stack_switch.stderr.diff ================================================= --- stack_switch.stderr.exp 2012-02-02 03:21:38.920426955 +0000 +++ stack_switch.stderr.out 2012-02-02 03:26:29.353820055 +0000 @@ -0,0 +1,3 @@ +Syscall param clone(child_tidptr) contains uninitialised byte(s) + ... +