Source: valgrind Version: 1:3.19.0-1 On amdhal.d.o:
% valgrind ./fails ==3527834== Memcheck, a memory error detector ==3527834== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==3527834== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==3527834== Command: ./fails ==3527834== ### unhandled dwarf2 abbrev form code 0x25 ### unhandled dwarf2 abbrev form code 0x25 ### unhandled dwarf2 abbrev form code 0x25 ### unhandled dwarf2 abbrev form code 0x23 get_Form_szB: unhandled 35 (DW_FORM_rnglistx) --3527834-- WARNING: Serious error when reading debug info --3527834-- When reading debug info from /home/malat/pr110643/fails: --3527834-- get_Form_contents: unhandled DW_FORM --3527834-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x92 valgrind: m_debuginfo/readdwarf.c:2761 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. host stacktrace: ==3527834== at 0x58040D44: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x58040E93: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x58040FFB: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x580C3BB7: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x580C3D53: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x580C91E3: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5807A497: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5806F613: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5809E927: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x580AB983: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5809AA1B: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5809647F: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x5809882F: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0x580DFC5F: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux) ==3527834== by 0xFFFFFFFFFFFFFFFF: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 222 (lwpid 3527834) ==3527834== at 0x401AB6C: __mmap64 (mmap64.c:58) ==3527834== by 0x401AB6C: mmap (mmap64.c:46) ==3527834== by 0x40066F3: _dl_map_segments (dl-map-segments.h:139) ==3527834== by 0x40066F3: _dl_map_object_from_fd (dl-load.c:1268) ==3527834== by 0x40078BF: _dl_map_object (dl-load.c:2272) ==3527834== by 0x400243B: openaux (dl-deps.c:64) ==3527834== by 0x40012FB: _dl_catch_exception (dl-catch.c:237) ==3527834== by 0x40028EB: _dl_map_object_deps (dl-deps.c:232) ==3527834== by 0x4017A47: dl_main (rtld.c:1972) ==3527834== by 0x4014E8B: _dl_sysdep_start (dl-sysdep.c:140) ==3527834== by 0x4016273: _dl_start_final (rtld.c:497) ==3527834== by 0x4016273: _dl_start (rtld.c:584) ==3527834== by 0x401A193: (below main) (dl-start.S:30) client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFEFFF130 valgrind stack range: [0x1002CC0000 0x1002DBFFFF] top usage: 17968 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. 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.
