SUMMARY Failed to start Valgrind bundled with Windows Manager (Enlightenment) STEPS TO REPRODUCE 1. Install enlightenment 2. Run `enlightenment_start -valgrind=1` and make sure the machine is running on aarch64 OBSERVED RESULT [arch@localhost ~]$ enlightenment_start -valgrind=1 E - PID=24164, valgrind=1 valgrind-command='/data/user/11/tech.ula/files/1/usr/bin/valgrind' ==24169== Memcheck, a memory error detector ==24169== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==24169== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==24169== Command: /data/user/11/tech.ula/files/1/usr/bin/enlightenment -valgrind=1 ==24169== valgrind: m_debuginfo/readdwarf.c:2544 (copy_convert_CfiExpr_tree): Assertion 'Unimplemented functionality' failed. valgrind: valgrind host stacktrace: ==24169== at 0x58040DB0: show_sched_status_wrk (m_libcassert.c:406) ==24169== by 0x58040F03: report_and_quit (m_libcassert.c:477) ==24169== by 0x58041077: vgPlain_assert_fail (m_libcassert.c:543) ==24169== by 0x580C1603: copy_convert_CfiExpr_tree.isra.0 (readdwarf.c:2544) ==24169== by 0x580C155F: copy_convert_CfiExpr_tree.isra.0 (readdwarf.c:2500) ==24169== by 0x580C1527: copy_convert_CfiExpr_tree.isra.0 (readdwarf.c:2493) ==24169== by 0x580C1B57: summarise_context (readdwarf.c:2280) ==24169== by 0x580C6287: run_CF_instructions (readdwarf.c:3655) ==24169== by 0x580C6287: vgModuleLocal_read_callframe_info_dwarf3 (readdwarf.c:4224) ==24169== by 0x5807BF1F: vgModuleLocal_read_elf_debug_info (readelf.c:3206) ==24169== by 0x5807032F: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:969) ==24169== by 0x5807032F: vgPlain_di_notify_mmap (debuginfo.c:1319) ==24169== by 0x5809E4C7: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2400) ==24169== by 0x580AA6E3: vgSysWrap_arm64_linux_sys_mmap_before (syswrap-arm64-linux.c:311) ==24169== by 0x5809A533: vgPlain_client_syscall (syswrap-main.c:1914) ==24169== by 0x58095F0B: handle_syscall (scheduler.c:1208) ==24169== by 0x580982C7: vgPlain_scheduler (scheduler.c:1526) ==24169== by 0x580E0FAF: thread_wrapper (syswrap-linux.c:101) ==24169== by 0x580E0FAF: run_a_thread_NORETURN (syswrap-linux.c:154) ==24169== by 0xFFFFFFFFFFFFFFFF: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 222 (lwpid 24169) ==24169== at 0x4018AEC: mmap (in /usr/lib/ld-2.32.so) ==24169== by 0x4007917: _dl_map_object_from_fd (in /usr/lib/ld-2.32.so) ==24169== by 0x4008967: _dl_map_object (in /usr/lib/ld-2.32.so) ==24169== by 0x400CBEF: openaux (in /usr/lib/ld-2.32.so) ==24169== by 0x40175F3: _dl_catch_exception (in /usr/lib/ld-2.32.so) ==24169== by 0x400D063: _dl_map_object_deps (in /usr/lib/ld-2.32.so) ==24169== by 0x400389F: dl_main (in /usr/lib/ld-2.32.so) ==24169== by 0x40165CF: _dl_sysdep_start (in /usr/lib/ld-2.32.so) ==24169== by 0x4001BF7: _dl_start_final (in /usr/lib/ld-2.32.so) ==24169== by 0x4001E37: _dl_start (in /usr/lib/ld-2.32.so) ==24169== by 0x400110B: ??? (in /usr/lib/ld-2.32.so) client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFEFFE740 valgrind stack range: [0x100908C000 0x100918BFFF] top usage: 17664 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. [arch@localhost ~]$ valgrind --version valgrind-3.16.1 EXPECTED RESULT Enlightenment running normally on X server SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Arch 4.4.192-perf-g6859189 (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Valgrind version: 3.16.1 ADDITIONAL INFORMATION The machine is running on ARM aarch64