Package: valgrind Version: 1:3.13.0-2.1 Severity: important Tags: upstream patch
Dear Maintainer, programs that link to BLAS library make valgrind fail with the assertion in the subject. It seems that upstream has solved it in https://bugs.kde.org/show_bug.cgi?id=398028#c13 Can you please backport the fix? Thanks! This is the complete error output: valgrind ./lapack ==26588== Memcheck, a memory error detector ==26588== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==26588== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==26588== Command: ./lapack ==26588== valgrind: m_debuginfo/debuginfo.c:551 (check_CFSI_related_invariants): Assertion 'cfsi_fits' failed. host stacktrace: ==26588== at 0x5804503A: show_sched_status_wrk (m_libcassert.c:355) ==26588== by 0x58045154: report_and_quit (m_libcassert.c:426) ==26588== by 0x580452D9: vgPlain_assert_fail (m_libcassert.c:492) ==26588== by 0x58079BEF: check_CFSI_related_invariants (debuginfo.c:551) ==26588== by 0x58079BEF: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:766) ==26588== by 0x58079BEF: vgPlain_di_notify_mmap (debuginfo.c:1061) ==26588== by 0x580A5381: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2388) ==26588== by 0x580DC2C4: vgSysWrap_amd64_linux_sys_mmap_before (syswrap-amd64-linux.c:400) ==26588== by 0x580A1B13: vgPlain_client_syscall (syswrap-main.c:1857) ==26588== by 0x5809E37A: handle_syscall (scheduler.c:1126) ==26588== by 0x5809FAA6: vgPlain_scheduler (scheduler.c:1443) ==26588== by 0x580AFC40: thread_wrapper (syswrap-linux.c:103) ==26588== by 0x580AFC40: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 26588) ==26588== at 0x401A693: mmap (mmap64.c:52) ==26588== by 0x40060AD: _dl_map_segments (dl-map-segments.h:94) ==26588== by 0x40060AD: _dl_map_object_from_fd (dl-load.c:1181) ==26588== by 0x400890E: _dl_map_object (dl-load.c:2461) ==26588== by 0x400D061: openaux (dl-deps.c:63) ==26588== by 0x401950A: _dl_catch_exception (dl-error-skeleton.c:196) ==26588== by 0x400D2F2: _dl_map_object_deps (dl-deps.c:249) ==26588== by 0x4003D95: dl_main (rtld.c:1726) ==26588== by 0x401862F: _dl_sysdep_start (dl-sysdep.c:253) ==26588== by 0x40020D7: _dl_start_final (rtld.c:414) ==26588== by 0x40020D7: _dl_start (rtld.c:521) ==26588== by 0x4001217: ??? (in /lib/x86_64-linux-gnu/ld-2.27.so) 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.
