================================================= ./valgrind-new/helgrind/tests/pth_barrier3.stderr.diff ================================================= --- pth_barrier3.stderr.exp 2012-03-31 03:36:44.642603822 +0100 +++ pth_barrier3.stderr.out 2012-03-31 03:45:23.866814941 +0100 @@ -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/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2012-03-31 03:36:45.176592960 +0100 +++ err_disable4.stderr.out 2012-03-31 03:41:21.380771723 +0100 @@ -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. @@ -349,1164 +350,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-03-31 03:36:45.078594954 +0100 +++ stack_switch.stderr.out 2012-03-31 03:41:41.916376410 +0100 @@ -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-03-31 03:21:54.944518946 +0100 +++ pth_barrier3.stderr.out 2012-03-31 03:31:30.993915920 +0100 @@ -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/err_disable4.stderr.diff ================================================= --- err_disable4.stderr.exp 2012-03-31 03:21:56.222492364 +0100 +++ err_disable4.stderr.out 2012-03-31 03:26:58.739200059 +0100 @@ -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. @@ -364,1149 +365,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-03-31 03:21:55.970497607 +0100 +++ stack_switch.stderr.out 2012-03-31 03:27:17.151817079 +0100 @@ -0,0 +1,3 @@ +Syscall param clone(child_tidptr) contains uninitialised byte(s) + ... +