================================================= ./valgrind-new/helgrind/tests/tc06_two_races_xml.stderr.diff ================================================= --- tc06_two_races_xml.stderr.exp 2010-09-09 03:29:25.000000000 +0100 +++ tc06_two_races_xml.stderr.out 2010-09-09 03:43:56.000000000 +0100 @@ -44,12 +44,10 @@ 0x........ ... - do_clone - - - 0x........ - ... pthread_create@@GLIBC_2.2.5 + ... + createthread.c + ... 0x........ @@ -121,6 +119,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -175,6 +176,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -229,6 +233,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -283,6 +290,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ ================================================= ./valgrind-new/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc23-amd64 ================================================= --- tc09_bad_unlock.stderr.exp-glibc23-amd64 2010-09-09 03:29:25.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:44:00.000000000 +0100 @@ -31,14 +31,13 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:49) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) +Thread #x's call to pthread_mutex_unlock failed + with error code 22 (EINVAL: Invalid argument) + at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) +--------------------- Thread #x unlocked a not-locked lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:27) @@ -46,6 +45,20 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:23) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Attempt to re-lock a non-recursive lock I already hold + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) Thread #x was created @@ -62,20 +75,21 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x unlocked an invalid lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:50) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) +Thread #x's call to pthread_mutex_unlock failed + with error code 22 (EINVAL: Invalid argument) + at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) +Thread #x: Exiting thread still holds 1 lock + ... + -ERROR SUMMARY: 8 errors from 8 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc25-amd64 ================================================= --- tc09_bad_unlock.stderr.exp-glibc25-amd64 2010-09-09 03:29:25.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:44:00.000000000 +0100 @@ -51,6 +51,10 @@ at 0x........: pthread_mutex_lock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion at 0x........: pthread_mutex_lock (hg_intercepts.c:...) ================================================= ./valgrind-new/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc25-x86 ================================================= --- tc09_bad_unlock.stderr.exp-glibc25-x86 2010-09-09 03:29:25.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:44:00.000000000 +0100 @@ -37,14 +37,7 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:49) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:49) - +--------------------- Thread #x unlocked a not-locked lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:27) @@ -52,6 +45,20 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:23) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Attempt to re-lock a non-recursive lock I already hold + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) Thread #x was created @@ -68,7 +75,7 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x unlocked an invalid lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) @@ -81,13 +88,8 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:50) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) +Thread #x: Exiting thread still holds 1 lock + ... -ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0) ================================================= ./valgrind-new/memcheck/tests/x86/insn_basic.stderr.diff ================================================= --- insn_basic.stderr.exp 2010-09-09 03:29:34.000000000 +0100 +++ insn_basic.stderr.out 2010-09-09 03:39:37.000000000 +0100 @@ -0,0 +1,46 @@ +16Uto64(t224) +vex: the `impossible' happened: + iselInt64Expr +vex storage: T total 221232732 bytes allocated +vex storage: P total 576 bytes allocated + +valgrind: the 'impossible' happened: + LibVEX called failure_exit(). + at 0x........: report_and_quit (m_libcassert.c:191) + by 0x........: panic (m_libcassert.c:275) + by 0x........: vgPlain_core_panic_at (m_libcassert.c:280) + by 0x........: vgPlain_core_panic (m_libcassert.c:285) + by 0x........: failure_exit (m_translate.c:674) + by 0x........: vpanic (main_util.c:226) + by 0x........: iselInt64Expr (host_x86_isel.c:2702) + by 0x........: iselCondCode (host_x86_isel.c:1782) + by 0x........: iselIntExpr_R (host_x86_isel.c:1188) + by 0x........: iselIntExpr_R (host_x86_isel.c:835) + by 0x........: iselIntExpr_R (host_x86_isel.c:1218) + by 0x........: iselIntExpr_RMI (host_x86_isel.c:1534) + by 0x........: iselSB_X86 (host_x86_isel.c:3785) + by 0x........: LibVEX_Translate (main_main.c:591) + by 0x........: vgPlain_translate (m_translate.c:1518) + by 0x........: vgPlain_scheduler (scheduler.c:867) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:94) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: divb_1 (insn_basic.c:17672) + by 0x........: main (insn_basic.c:44564) + + +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/memcheck/tests/x86/insn_basic.stdout.diff ================================================= --- insn_basic.stdout.exp 2010-09-09 03:29:34.000000000 +0100 +++ insn_basic.stdout.out 2010-09-09 03:39:36.000000000 +0100 @@ -283,774 +283,4 @@ cmpw_60 ... ok cmpw_61 ... ok cmpw_62 ... ok -cmpw_63 ... ok -cmpw_64 ... ok -cmpw_65 ... ok -cmpw_66 ... ok -cmpw_67 ... ok -cmpw_68 ... ok -cmpw_69 ... ok -cmpw_70 ... ok -cmpw_71 ... ok -cmpw_72 ... ok -cmpw_73 ... ok -cmpw_74 ... ok -cmpw_75 ... ok -cmpw_76 ... ok -cmpw_77 ... ok -cmpw_78 ... ok -cmpw_79 ... ok -cmpw_80 ... ok -cmpl_1 ... ok -cmpl_2 ... ok -cmpl_3 ... ok -cmpl_4 ... ok -cmpl_5 ... ok -cmpl_6 ... ok -cmpl_7 ... ok -cmpl_8 ... ok -cmpl_9 ... ok -cmpl_10 ... ok -cmpl_11 ... ok -cmpl_12 ... ok -cmpl_13 ... ok -cmpl_14 ... ok -cmpl_15 ... ok -cmpl_16 ... ok -cmpl_17 ... ok -cmpl_18 ... ok -cmpl_19 ... ok -cmpl_20 ... ok -cmpl_21 ... ok -cmpl_22 ... ok -cmpl_23 ... ok -cmpl_24 ... ok -cmpl_25 ... ok -cmpl_26 ... ok -cmpl_27 ... ok -cmpl_28 ... ok -cmpl_29 ... ok -cmpl_30 ... ok -cmpl_31 ... ok -cmpl_32 ... ok -cmpl_33 ... ok -cmpl_34 ... ok -cmpl_35 ... ok -cmpl_36 ... ok -cmpl_37 ... ok -cmpl_38 ... ok -cmpl_39 ... ok -cmpl_40 ... ok -cmpl_41 ... ok -cmpl_42 ... ok -cmpl_43 ... ok -cmpl_44 ... ok -cmpl_45 ... ok -cmpl_46 ... ok -cmpl_47 ... ok -cmpl_48 ... ok -cmpl_49 ... ok -cmpl_50 ... ok -cmpl_51 ... ok -cmpl_52 ... ok -cmpl_53 ... ok -cmpl_54 ... ok -cmpl_55 ... ok -cmpl_56 ... ok -cmpl_57 ... ok -cmpl_58 ... ok -cmpl_59 ... ok -cmpl_60 ... ok -cmpl_61 ... ok -cmpl_62 ... ok -cmpl_63 ... ok -cmpl_64 ... ok -cmpl_65 ... ok -cmpl_66 ... ok -cmpl_67 ... ok -cmpl_68 ... ok -cmpl_69 ... ok -cmpl_70 ... ok -cmpl_71 ... ok -cmpl_72 ... ok -cmpl_73 ... ok -cmpl_74 ... ok -cmpl_75 ... ok -cmpl_76 ... ok ================================================= ./valgrind-new/none/tests/amd64/bug132918.stdout.diff ================================================= --- bug132918.stdout.exp 2010-09-09 03:29:31.000000000 +0100 +++ bug132918.stdout.out 2010-09-09 03:41:09.000000000 +0100 @@ -1,6 +1,6 @@ xx1 -> 0x4200 8.300000 xx2 -> 0x0000 1.440000 -xx -> 0x0000 -nan +xx -> 0x0000 nan xx -> 0x0000 0.809017 xx -> 0x0000 0.309018 xx -> 0x0000 -0.309015 ================================================= ./valgrind-new/none/tests/amd64/fxtract.stdout.diff ================================================= --- fxtract.stdout.exp 2010-09-09 03:29:31.000000000 +0100 +++ fxtract.stdout.out 2010-09-09 03:41:11.000000000 +0100 @@ -40,7 +40,7 @@ 2.7049662808e+02 -> 1.0566274534 8.0000000000 0.0000000000e+00 -> 0.0000000000 -inf inf -> inf inf - -nan -> -nan -nan + nan -> nan nan 7.2124891681e-308 -> 1.6207302828 -1021.0000000000 5.7982756057e-308 -> 1.3029400313 -1021.0000000000 4.3840620434e-308 -> 1.9702995595 -1022.0000000000 ================================================= ./valgrind-new/none/tests/x86/fxtract.stdout.diff ================================================= --- fxtract.stdout.exp 2010-09-09 03:29:34.000000000 +0100 +++ fxtract.stdout.out 2010-09-09 03:42:40.000000000 +0100 @@ -40,7 +40,7 @@ 2.7049662808e+02 -> 1.0566274534 8.0000000000 0.0000000000e+00 -> 0.0000000000 -inf inf -> inf inf - -nan -> -nan -nan + nan -> nan nan 7.2124891681e-308 -> 1.6207302828 -1021.0000000000 5.7982756057e-308 -> 1.3029400313 -1021.0000000000 4.3840620434e-308 -> 1.9702995595 -1022.0000000000 ================================================= ./valgrind-new/none/tests/x86/insn_basic.stderr.diff ================================================= --- insn_basic.stderr.exp 2010-09-09 03:29:34.000000000 +0100 +++ insn_basic.stderr.out 2010-09-09 03:42:41.000000000 +0100 @@ -0,0 +1,42 @@ +16Uto64(t18) +vex: the `impossible' happened: + iselInt64Expr +vex storage: T total 56835892 bytes allocated +vex storage: P total 576 bytes allocated + +valgrind: the 'impossible' happened: + LibVEX called failure_exit(). + at 0x........: report_and_quit (m_libcassert.c:191) + by 0x........: panic (m_libcassert.c:275) + by 0x........: vgPlain_core_panic_at (m_libcassert.c:280) + by 0x........: vgPlain_core_panic (m_libcassert.c:285) + by 0x........: failure_exit (m_translate.c:674) + by 0x........: vpanic (main_util.c:226) + by 0x........: iselInt64Expr (host_x86_isel.c:2702) + by 0x........: iselInt64Expr (host_x86_isel.c:2085) + by 0x........: iselSB_X86 (host_x86_isel.c:3792) + by 0x........: LibVEX_Translate (main_main.c:591) + by 0x........: vgPlain_translate (m_translate.c:1518) + by 0x........: vgPlain_scheduler (scheduler.c:867) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:94) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: divb_1 (insn_basic.c:17672) + by 0x........: main (insn_basic.c:44564) + + +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/x86/insn_basic.stdout.diff ================================================= --- insn_basic.stdout.exp 2010-09-09 03:29:34.000000000 +0100 +++ insn_basic.stdout.out 2010-09-09 03:42:41.000000000 +0100 @@ -283,774 +283,4 @@ cmpw_60 ... ok cmpw_61 ... ok cmpw_62 ... ok -cmpw_63 ... ok -cmpw_64 ... ok -cmpw_65 ... ok -cmpw_66 ... ok -cmpw_67 ... ok -cmpw_68 ... ok -cmpw_69 ... ok -cmpw_70 ... ok -cmpw_71 ... ok -cmpw_72 ... ok -cmpw_73 ... ok -cmpw_74 ... ok -cmpw_75 ... ok -cmpw_76 ... ok -cmpw_77 ... ok -cmpw_78 ... ok -cmpw_79 ... ok -cmpw_80 ... ok -cmpl_1 ... ok -cmpl_2 ... ok -cmpl_3 ... ok -cmpl_4 ... ok -cmpl_5 ... ok -cmpl_6 ... ok -cmpl_7 ... ok -cmpl_8 ... ok -cmpl_9 ... ok -cmpl_10 ... ok -cmpl_11 ... ok -cmpl_12 ... ok -cmpl_13 ... ok -cmpl_14 ... ok -cmpl_15 ... ok -cmpl_16 ... ok -cmpl_17 ... ok -cmpl_18 ... ok -cmpl_19 ... ok -cmpl_20 ... ok -cmpl_21 ... ok -cmpl_22 ... ok -cmpl_23 ... ok -cmpl_24 ... ok -cmpl_25 ... ok -cmpl_26 ... ok -cmpl_27 ... ok -cmpl_28 ... ok -cmpl_29 ... ok -cmpl_30 ... ok -cmpl_31 ... ok -cmpl_32 ... ok -cmpl_33 ... ok -cmpl_34 ... ok -cmpl_35 ... ok -cmpl_36 ... ok -cmpl_37 ... ok -cmpl_38 ... ok -cmpl_39 ... ok -cmpl_40 ... ok -cmpl_41 ... ok -cmpl_42 ... ok -cmpl_43 ... ok -cmpl_44 ... ok -cmpl_45 ... ok -cmpl_46 ... ok -cmpl_47 ... ok -cmpl_48 ... ok -cmpl_49 ... ok -cmpl_50 ... ok -cmpl_51 ... ok -cmpl_52 ... ok -cmpl_53 ... ok -cmpl_54 ... ok -cmpl_55 ... ok -cmpl_56 ... ok -cmpl_57 ... ok -cmpl_58 ... ok -cmpl_59 ... ok -cmpl_60 ... ok -cmpl_61 ... ok -cmpl_62 ... ok -cmpl_63 ... ok -cmpl_64 ... ok -cmpl_65 ... ok -cmpl_66 ... ok -cmpl_67 ... ok -cmpl_68 ... ok -cmpl_69 ... ok -cmpl_70 ... ok -cmpl_71 ... ok -cmpl_72 ... ok -cmpl_73 ... ok -cmpl_74 ... ok -cmpl_75 ... ok -cmpl_76 ... ok ================================================= ./valgrind-old/helgrind/tests/tc06_two_races_xml.stderr.diff ================================================= --- tc06_two_races_xml.stderr.exp 2010-09-09 03:05:23.000000000 +0100 +++ tc06_two_races_xml.stderr.out 2010-09-09 03:20:52.000000000 +0100 @@ -44,12 +44,10 @@ 0x........ ... - do_clone - - - 0x........ - ... pthread_create@@GLIBC_2.2.5 + ... + createthread.c + ... 0x........ @@ -121,6 +119,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -175,6 +176,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -229,6 +233,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ @@ -283,6 +290,9 @@ 0x........ ... start_thread + ... + pthread_create.c + ... 0x........ ================================================= ./valgrind-old/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc23-amd64 ================================================= --- tc09_bad_unlock.stderr.exp-glibc23-amd64 2010-09-09 03:05:23.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:20:55.000000000 +0100 @@ -31,14 +31,13 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:49) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) +Thread #x's call to pthread_mutex_unlock failed + with error code 22 (EINVAL: Invalid argument) + at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) +--------------------- Thread #x unlocked a not-locked lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:27) @@ -46,6 +45,20 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:23) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Attempt to re-lock a non-recursive lock I already hold + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) Thread #x was created @@ -62,20 +75,21 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x unlocked an invalid lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:50) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) +Thread #x's call to pthread_mutex_unlock failed + with error code 22 (EINVAL: Invalid argument) + at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) +Thread #x: Exiting thread still holds 1 lock + ... + -ERROR SUMMARY: 8 errors from 8 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc25-amd64 ================================================= --- tc09_bad_unlock.stderr.exp-glibc25-amd64 2010-09-09 03:05:23.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:20:55.000000000 +0100 @@ -51,6 +51,10 @@ at 0x........: pthread_mutex_lock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion at 0x........: pthread_mutex_lock (hg_intercepts.c:...) ================================================= ./valgrind-old/helgrind/tests/tc09_bad_unlock.stderr.diff-glibc25-x86 ================================================= --- tc09_bad_unlock.stderr.exp-glibc25-x86 2010-09-09 03:05:23.000000000 +0100 +++ tc09_bad_unlock.stderr.out 2010-09-09 03:20:55.000000000 +0100 @@ -37,14 +37,7 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:49) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:49) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:49) - +--------------------- Thread #x unlocked a not-locked lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:27) @@ -52,6 +45,20 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:23) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Attempt to re-lock a non-recursive lock I already hold + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:50) + Lock was previously acquired + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) + by 0x........: main (tc09_bad_unlock.c:49) + +Thread #x: Bug in libpthread: recursive write lock granted on mutex/wrlock which does not support recursion + at 0x........: pthread_mutex_lock (hg_intercepts.c:...) + by 0x........: nearly_main (tc09_bad_unlock.c:32) by 0x........: main (tc09_bad_unlock.c:50) Thread #x was created @@ -68,7 +75,7 @@ Lock at 0x........ was first observed at 0x........: pthread_mutex_init (hg_intercepts.c:...) by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) + by 0x........: main (tc09_bad_unlock.c:49) Thread #x unlocked an invalid lock at 0x........ at 0x........: pthread_mutex_unlock (hg_intercepts.c:...) @@ -81,13 +88,8 @@ by 0x........: nearly_main (tc09_bad_unlock.c:41) by 0x........: main (tc09_bad_unlock.c:50) -Thread #x deallocated location 0x........ containing a locked lock - at 0x........: nearly_main (tc09_bad_unlock.c:45) - by 0x........: main (tc09_bad_unlock.c:50) - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: nearly_main (tc09_bad_unlock.c:31) - by 0x........: main (tc09_bad_unlock.c:50) +Thread #x: Exiting thread still holds 1 lock + ... -ERROR SUMMARY: 10 errors from 10 contexts (suppressed: 0 from 0) +ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0) ================================================= ./valgrind-old/memcheck/tests/x86/insn_basic.stderr.diff ================================================= --- insn_basic.stderr.exp 2010-09-09 03:06:11.000000000 +0100 +++ insn_basic.stderr.out 2010-09-09 03:16:25.000000000 +0100 @@ -0,0 +1,46 @@ +16Uto64(t224) +vex: the `impossible' happened: + iselInt64Expr +vex storage: T total 221272004 bytes allocated +vex storage: P total 576 bytes allocated + +valgrind: the 'impossible' happened: + LibVEX called failure_exit(). + at 0x........: report_and_quit (m_libcassert.c:191) + by 0x........: panic (m_libcassert.c:275) + by 0x........: vgPlain_core_panic_at (m_libcassert.c:280) + by 0x........: vgPlain_core_panic (m_libcassert.c:285) + by 0x........: failure_exit (m_translate.c:674) + by 0x........: vpanic (main_util.c:226) + by 0x........: iselInt64Expr (host_x86_isel.c:2702) + by 0x........: iselCondCode (host_x86_isel.c:1782) + by 0x........: iselIntExpr_R (host_x86_isel.c:1188) + by 0x........: iselIntExpr_R (host_x86_isel.c:835) + by 0x........: iselIntExpr_R (host_x86_isel.c:1218) + by 0x........: iselIntExpr_RMI (host_x86_isel.c:1534) + by 0x........: iselSB_X86 (host_x86_isel.c:3785) + by 0x........: LibVEX_Translate (main_main.c:591) + by 0x........: vgPlain_translate (m_translate.c:1518) + by 0x........: vgPlain_scheduler (scheduler.c:867) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:94) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: divb_1 (insn_basic.c:17672) + by 0x........: main (insn_basic.c:44564) + + +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/memcheck/tests/x86/insn_basic.stdout.diff ================================================= --- insn_basic.stdout.exp 2010-09-09 03:06:11.000000000 +0100 +++ insn_basic.stdout.out 2010-09-09 03:16:25.000000000 +0100 @@ -283,774 +283,4 @@ cmpw_60 ... ok cmpw_61 ... ok cmpw_62 ... ok -cmpw_63 ... ok -cmpw_64 ... ok -cmpw_65 ... ok -cmpw_66 ... ok -cmpw_67 ... ok -cmpw_68 ... ok -cmpw_69 ... ok -cmpw_70 ... ok -cmpw_71 ... ok -cmpw_72 ... ok -cmpw_73 ... ok -cmpw_74 ... ok -cmpw_75 ... ok -cmpw_76 ... ok -cmpw_77 ... ok -cmpw_78 ... ok -cmpw_79 ... ok -cmpw_80 ... ok -cmpl_1 ... ok -cmpl_2 ... ok -cmpl_3 ... ok -cmpl_4 ... ok -cmpl_5 ... ok -cmpl_6 ... ok -cmpl_7 ... ok -cmpl_8 ... ok -cmpl_9 ... ok -cmpl_10 ... ok -cmpl_11 ... ok -cmpl_12 ... ok -cmpl_13 ... ok -cmpl_14 ... ok -cmpl_15 ... ok -cmpl_16 ... ok -cmpl_17 ... ok -cmpl_18 ... ok -cmpl_19 ... ok -cmpl_20 ... ok -cmpl_21 ... ok -cmpl_22 ... ok -cmpl_23 ... ok -cmpl_24 ... ok -cmpl_25 ... ok -cmpl_26 ... ok -cmpl_27 ... ok -cmpl_28 ... ok -cmpl_29 ... ok -cmpl_30 ... ok -cmpl_31 ... ok -cmpl_32 ... ok -cmpl_33 ... ok -cmpl_34 ... ok -cmpl_35 ... ok -cmpl_36 ... ok -cmpl_37 ... ok -cmpl_38 ... ok -cmpl_39 ... ok -cmpl_40 ... ok -cmpl_41 ... ok -cmpl_42 ... ok -cmpl_43 ... ok -cmpl_44 ... ok -cmpl_45 ... ok -cmpl_46 ... ok -cmpl_47 ... ok -cmpl_48 ... ok -cmpl_49 ... ok -cmpl_50 ... ok -cmpl_51 ... ok -cmpl_52 ... ok -cmpl_53 ... ok -cmpl_54 ... ok -cmpl_55 ... ok -cmpl_56 ... ok -cmpl_57 ... ok -cmpl_58 ... ok -cmpl_59 ... ok -cmpl_60 ... ok -cmpl_61 ... ok -cmpl_62 ... ok -cmpl_63 ... ok -cmpl_64 ... ok -cmpl_65 ... ok -cmpl_66 ... ok -cmpl_67 ... ok -cmpl_68 ... ok -cmpl_69 ... ok -cmpl_70 ... ok -cmpl_71 ... ok -cmpl_72 ... ok -cmpl_73 ... ok -cmpl_74 ... ok -cmpl_75 ... ok -cmpl_76 ... ok ================================================= ./valgrind-old/none/tests/amd64/bug132918.stdout.diff ================================================= --- bug132918.stdout.exp 2010-09-09 03:06:02.000000000 +0100 +++ bug132918.stdout.out 2010-09-09 03:18:02.000000000 +0100 @@ -1,6 +1,6 @@ xx1 -> 0x4200 8.300000 xx2 -> 0x0000 1.440000 -xx -> 0x0000 -nan +xx -> 0x0000 nan xx -> 0x0000 0.809017 xx -> 0x0000 0.309018 xx -> 0x0000 -0.309015 ================================================= ./valgrind-old/none/tests/amd64/fxtract.stdout.diff ================================================= --- fxtract.stdout.exp 2010-09-09 03:06:02.000000000 +0100 +++ fxtract.stdout.out 2010-09-09 03:18:05.000000000 +0100 @@ -40,7 +40,7 @@ 2.7049662808e+02 -> 1.0566274534 8.0000000000 0.0000000000e+00 -> 0.0000000000 -inf inf -> inf inf - -nan -> -nan -nan + nan -> nan nan 7.2124891681e-308 -> 1.6207302828 -1021.0000000000 5.7982756057e-308 -> 1.3029400313 -1021.0000000000 4.3840620434e-308 -> 1.9702995595 -1022.0000000000 ================================================= ./valgrind-old/none/tests/x86/fxtract.stdout.diff ================================================= --- fxtract.stdout.exp 2010-09-09 03:06:11.000000000 +0100 +++ fxtract.stdout.out 2010-09-09 03:19:35.000000000 +0100 @@ -40,7 +40,7 @@ 2.7049662808e+02 -> 1.0566274534 8.0000000000 0.0000000000e+00 -> 0.0000000000 -inf inf -> inf inf - -nan -> -nan -nan + nan -> nan nan 7.2124891681e-308 -> 1.6207302828 -1021.0000000000 5.7982756057e-308 -> 1.3029400313 -1021.0000000000 4.3840620434e-308 -> 1.9702995595 -1022.0000000000 ================================================= ./valgrind-old/none/tests/x86/insn_basic.stderr.diff ================================================= --- insn_basic.stderr.exp 2010-09-09 03:06:11.000000000 +0100 +++ insn_basic.stderr.out 2010-09-09 03:19:36.000000000 +0100 @@ -0,0 +1,42 @@ +16Uto64(t18) +vex: the `impossible' happened: + iselInt64Expr +vex storage: T total 56835892 bytes allocated +vex storage: P total 576 bytes allocated + +valgrind: the 'impossible' happened: + LibVEX called failure_exit(). + at 0x........: report_and_quit (m_libcassert.c:191) + by 0x........: panic (m_libcassert.c:275) + by 0x........: vgPlain_core_panic_at (m_libcassert.c:280) + by 0x........: vgPlain_core_panic (m_libcassert.c:285) + by 0x........: failure_exit (m_translate.c:674) + by 0x........: vpanic (main_util.c:226) + by 0x........: iselInt64Expr (host_x86_isel.c:2702) + by 0x........: iselInt64Expr (host_x86_isel.c:2085) + by 0x........: iselSB_X86 (host_x86_isel.c:3792) + by 0x........: LibVEX_Translate (main_main.c:591) + by 0x........: vgPlain_translate (m_translate.c:1518) + by 0x........: vgPlain_scheduler (scheduler.c:867) + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:94) + +sched status: + running_tid=1 + +Thread 1: status = VgTs_Runnable + at 0x........: divb_1 (insn_basic.c:17672) + by 0x........: main (insn_basic.c:44564) + + +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/x86/insn_basic.stdout.diff ================================================= --- insn_basic.stdout.exp 2010-09-09 03:06:11.000000000 +0100 +++ insn_basic.stdout.out 2010-09-09 03:19:36.000000000 +0100 @@ -283,774 +283,4 @@ cmpw_60 ... ok cmpw_61 ... ok cmpw_62 ... ok -cmpw_63 ... ok -cmpw_64 ... ok -cmpw_65 ... ok -cmpw_66 ... ok -cmpw_67 ... ok -cmpw_68 ... ok -cmpw_69 ... ok -cmpw_70 ... ok -cmpw_71 ... ok -cmpw_72 ... ok -cmpw_73 ... ok -cmpw_74 ... ok -cmpw_75 ... ok -cmpw_76 ... ok -cmpw_77 ... ok -cmpw_78 ... ok -cmpw_79 ... ok -cmpw_80 ... ok -cmpl_1 ... ok -cmpl_2 ... ok -cmpl_3 ... ok -cmpl_4 ... ok -cmpl_5 ... ok -cmpl_6 ... ok -cmpl_7 ... ok -cmpl_8 ... ok -cmpl_9 ... ok -cmpl_10 ... ok -cmpl_11 ... ok -cmpl_12 ... ok -cmpl_13 ... ok -cmpl_14 ... ok -cmpl_15 ... ok -cmpl_16 ... ok -cmpl_17 ... ok -cmpl_18 ... ok -cmpl_19 ... ok -cmpl_20 ... ok -cmpl_21 ... ok -cmpl_22 ... ok -cmpl_23 ... ok -cmpl_24 ... ok -cmpl_25 ... ok -cmpl_26 ... ok -cmpl_27 ... ok -cmpl_28 ... ok -cmpl_29 ... ok -cmpl_30 ... ok -cmpl_31 ... ok -cmpl_32 ... ok -cmpl_33 ... ok -cmpl_34 ... ok -cmpl_35 ... ok -cmpl_36 ... ok -cmpl_37 ... ok -cmpl_38 ... ok -cmpl_39 ... ok -cmpl_40 ... ok -cmpl_41 ... ok -cmpl_42 ... ok -cmpl_43 ... ok -cmpl_44 ... ok -cmpl_45 ... ok -cmpl_46 ... ok -cmpl_47 ... ok -cmpl_48 ... ok -cmpl_49 ... ok -cmpl_50 ... ok -cmpl_51 ... ok -cmpl_52 ... ok -cmpl_53 ... ok -cmpl_54 ... ok -cmpl_55 ... ok -cmpl_56 ... ok -cmpl_57 ... ok -cmpl_58 ... ok -cmpl_59 ... ok -cmpl_60 ... ok -cmpl_61 ... ok -cmpl_62 ... ok -cmpl_63 ... ok -cmpl_64 ... ok -cmpl_65 ... ok -cmpl_66 ... ok -cmpl_67 ... ok -cmpl_68 ... ok -cmpl_69 ... ok -cmpl_70 ... ok -cmpl_71 ... ok -cmpl_72 ... ok -cmpl_73 ... ok -cmpl_74 ... ok -cmpl_75 ... ok -cmpl_76 ... ok