Re: [Valgrind-users] [help] I run the pocl , memcheck report this error (the red text), what it meant.
On Thu, 2018-04-19 at 00:39 +, Wuweijia wrote: > memcheck expensive sanity: distinguished_secondaries have changed > > valgrind: external/valgrind/coregrind/m_scheduler/scheduler.c:2240 > (vgPlain_sanity_check_general): Assertion > 'VG_TDICT_CALL(tool_expensive_sanity_check)' failed. > > host stacktrace: > ==4540== at 0x3803AA8C: show_sched_status_wrk (m_libcassert.c:343) > ==4540== by 0x3803AD07: report_and_quit (m_libcassert.c:419) > ==4540== by 0x3803AD07: vgPlain_assert_fail (m_libcassert.c:485) > ==4540== by 0x3808119B: vgPlain_sanity_check_general (scheduler.c:2240) > ==4540== by 0x3808142F: vgPlain_scheduler (scheduler.c:1308) > ==4540== by 0x3808E307: thread_wrapper (syswrap-linux.c:103) > ==4540== by 0x3808E307: run_a_thread_NORETURN (syswrap-linux.c:156) > ==4540== by 0x3808E6CF: vgModuleLocal_start_thread_NORETURN > (syswrap-linux.c:325) > ==4540== by 0x380B4143: ??? (in > /system/lib64/valgrind/memcheck-arm64-linux) > The above is a valgrind self-check/sanity check that detects an internal corruption in its own internal memcheck data structure. Never seen this assert failing up to now. This might be * a bug in valgrind itself * (less likely) a nasty bug in your application that succeeded to corrupt valgrind memcheck data structures Was there any application error reported by Valgrind before this failing self-check ? * (less likely?) an hardware problem, such as failing memory ? Philippe -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
[Valgrind-users] [help] I run the pocl , memcheck report this error (the red text), what it meant.
[2018-04-15 23:44:37] [HSN_RAW_AP][I] setup_opencl_hdrp : 175 cl_path_name = /system/bin/ pocl_llvm_build_program: Final options: -Dcl_khr_byte_addressable_store -Dcl_khr_global_int32_base_atomics -Dcl_khr_global_int32_extended_atomics -Dcl_khr_local_int32_base_atomics -Dcl_khr_local_int32_extended_atomics -Dcl_khr_spir -Dcl_khr_fp16 -Dcl_khr_int64 -Dcl_khr_fp64 -Dcl_khr_int64_base_atomics -Dcl_khr_int64_extended_atomics -O0 -x cl -Dinline= -I. -D__ENDIAN_LITTLE__=1 -D__IMAGE_SUPPORT__=1 -DCL_DEVICE_MAX_GLOBAL_VARIABLE_SIZE=0 -D__OPENCL_VERSION__=200 -cl-std=CL2.0 -D__OPENCL_C_VERSION__=200 -fno-builtin -ffp-contract=off -triple=aarch64-unknown-linux-android -target-cpu generic ### options: -Dcl_khr_byte_addressable_store -Dcl_khr_global_int32_base_atomics -Dcl_khr_global_int32_extended_atomics -Dcl_khr_local_int32_base_atomics -Dcl_khr_local_int32_extended_atomics -Dcl_khr_spir -Dcl_khr_fp16 -Dcl_khr_int64 -Dcl_khr_fp64 -Dcl_khr_int64_base_atomics -Dcl_khr_int64_extended_atomics -O0 -x cl -Dinline= -I. -D__ENDIAN_LITTLE__=1 -D__IMAGE_SUPPORT__=1 -DCL_DEVICE_MAX_GLOBAL_VARIABLE_SIZE=0 -D__OPENCL_VERSION__=200 -cl-std=CL2.0 -D__OPENCL_C_VERSION__=200 -fno-builtin -ffp-contract=off -triple=aarch64-unknown-linux-android -target-cpu generic user_options: memcheck expensive sanity: distinguished_secondaries have changed valgrind: external/valgrind/coregrind/m_scheduler/scheduler.c:2240 (vgPlain_sanity_check_general): Assertion 'VG_TDICT_CALL(tool_expensive_sanity_check)' failed. host stacktrace: ==4540==at 0x3803AA8C: show_sched_status_wrk (m_libcassert.c:343) ==4540==by 0x3803AD07: report_and_quit (m_libcassert.c:419) ==4540==by 0x3803AD07: vgPlain_assert_fail (m_libcassert.c:485) ==4540==by 0x3808119B: vgPlain_sanity_check_general (scheduler.c:2240) ==4540==by 0x3808142F: vgPlain_scheduler (scheduler.c:1308) ==4540==by 0x3808E307: thread_wrapper (syswrap-linux.c:103) ==4540==by 0x3808E307: run_a_thread_NORETURN (syswrap-linux.c:156) ==4540==by 0x3808E6CF: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:325) ==4540==by 0x380B4143: ??? (in /system/lib64/valgrind/memcheck-arm64-linux) sched status: running_tid=10 Thread 1: status = VgTs_WaitSys (lwpid 4540) Thread 2: status = VgTs_WaitSys (lwpid 4541) Thread 3: status = VgTs_WaitSys (lwpid 4543) Thread 4: status = VgTs_WaitSys (lwpid 4544) Thread 5: status = VgTs_WaitSys (lwpid 4545) Thread 6: status = VgTs_WaitSys (lwpid 4546) Thread 7: status = VgTs_WaitSys (lwpid 4547) Thread 8: status = VgTs_WaitSys (lwpid 4548) Thread 9: status = VgTs_WaitSys (lwpid 4549) Thread 10: status = VgTs_Runnable (lwpid 4550) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
