https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #24 from Austin English <austinengl...@gmail.com> --- Getting a failed assertion in some tests: valgrind: m_debuginfo/debuginfo.c:694 (check_CFSI_related_invariants): Assertion '!ranges_overlap(map->avma, map->size, map2->avma, map2->size)' failed. valgrind: DiCfsi invariant (1) verification failed host stacktrace: ==6286== at 0x58041CF9: show_sched_status_wrk (m_libcassert.c:406) ==6286== by 0x58041E20: report_and_quit (m_libcassert.c:477) ==6286== by 0x58041F14: vgPlain_assert_fail (m_libcassert.c:543) ==6286== by 0x58075670: check_CFSI_related_invariants (debuginfo.c:692) ==6286== by 0x58075670: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:992) ==6286== by 0x58075670: vgPlain_di_notify_mmap (debuginfo.c:1326) ==6286== by 0x580A8D51: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2400) ==6286== by 0x580B5F25: vgSysWrap_x86_linux_sys_mmap2_before (syswrap-x86-linux.c:987) ==6286== by 0x580A45BE: vgPlain_client_syscall (syswrap-main.c:1914) ==6286== by 0x580A090C: handle_syscall (scheduler.c:1208) ==6286== by 0x580A246F: vgPlain_scheduler (scheduler.c:1526) ==6286== by 0x580F7312: thread_wrapper (syswrap-linux.c:101) ==6286== by 0x580F7312: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 192 (lwpid 6286) ==6286== at 0x435A253: mmap64 (mmap64.c:56) ==6286== by 0x7BCAAFFE: map_pe_header (virtual.c:1491) ==6286== by 0x7BCAC3E6: map_image (virtual.c:1569) ==6286== by 0x7BCADA02: virtual_map_section (virtual.c:1838) ==6286== by 0x7BC68BFC: open_dll_file (loader.c:2515) ==6286== by 0x7BC68DA8: search_dll_file (loader.c:3074) ==6286== by 0x7BC6923F: find_dll_file (loader.c:3154) ==6286== by 0x7BC6CBF9: load_dll (loader.c:3186) ==6286== by 0x7BC6C0F8: import_dll (loader.c:801) ==6286== by 0x7BC6C64B: fixup_imports (loader.c:1165) ==6286== by 0x7BC6C8AF: load_native_dll (loader.c:2570) ==6286== by 0x7BC6CB26: load_builtin_dll (loader.c:2930) ==6286== by 0x7BC6CE08: load_dll (loader.c:3231) ==6286== by 0x7BC6C0F8: import_dll (loader.c:801) ==6286== by 0x7BC6C64B: fixup_imports (loader.c:1165) ==6286== by 0x7BC6E372: LdrInitializeThunk (loader.c:3987) ==6286== by 0x7BC99953: attach_thread (signal_i386.c:3050) ==6286== by 0x7BC9634F: ??? (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) client stack range: [0x4A62000 0x4B5FFFF] client SP: 0x4B5D22C valgrind stack range: [0x881D3000 0x882D2FFF] top usage: 7092 of 1048576 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. e.g., avifil32/tests/api.c -- You are receiving this mail because: You are watching all bug changes.
