https://bugs.kde.org/show_bug.cgi?id=461074
--- Comment #3 from Mathieu Malaterre <ma...@debian.org> ---
(In reply to Mark Wielaard from comment #2)
> The first issue seems to be because we cannot handle the CFI from this
> libamath.so library.
> For the second it isn't clear which library causes the issue. Could you
> rerun with -v ?
Sorry for being sloppy here.
Here you:
% valgrind -v ./fails
==284860== Memcheck, a memory error detector
==284860== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==284860== Using Valgrind-3.19.0-8d3c8034b8-20220411 and LibVEX; rerun with -h
for copyright info
==284860== Command: ./fails
==284860==
--284860-- Valgrind options:
--284860-- -v
--284860-- Contents of /proc/version:
--284860-- Linux version 5.10.0-25-arm64 (debian-ker...@lists.debian.org)
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian)
2.35.2) #1 SMP Debian 5.10.191-1 (2023-08-16)
--284860--
--284860-- Arch and hwcaps: ARM64, LittleEndian, v8
--284860-- Page sizes: currently 4096, max supported 65536
--284860-- Valgrind library directory: /usr/libexec/valgrind
--284860-- Reading syms from /home/malat/pr110643/fails
--284860-- Reading syms from /lib/aarch64-linux-gnu/ld-linux-aarch64.so.1
--284860-- Considering
/usr/lib/debug/.build-id/e3/1f8e686f102995033b5b17cc829c67c7efbc90.debug ..
--284860-- .. build-id is valid
--284860-- Reading syms from /usr/libexec/valgrind/memcheck-arm64-linux
--284860-- object doesn't have a symbol table
--284860-- object doesn't have a dynamic symbol table
--284860-- Scheduler: using generic scheduler lock implementation.
--284860-- Reading suppressions file: /usr/libexec/valgrind/default.supp
==284860== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-284860-by-malat-on-???
==284860== embedded gdbserver: writing to
/tmp/vgdb-pipe-to-vgdb-from-284860-by-malat-on-???
==284860== embedded gdbserver: shared mem
/tmp/vgdb-pipe-shared-mem-vgdb-284860-by-malat-on-???
==284860==
==284860== TO CONTROL THIS PROCESS USING vgdb (which you probably
==284860== don't want to do, unless you know exactly what you're doing,
==284860== or are doing some strange experiment):
==284860== /usr/bin/vgdb --pid=284860 ...command...
==284860==
==284860== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==284860== /path/to/gdb ./fails
==284860== and then give GDB the following command
==284860== target remote | /usr/bin/vgdb --pid=284860
==284860== --pid is optional if only one valgrind process is running
==284860==
--284860-- REDIR: 0x401c080 (ld-linux-aarch64.so.1:strlen) redirected to
0x580bb9f4 (???)
--284860-- REDIR: 0x401b7c0 (ld-linux-aarch64.so.1:strcmp) redirected to
0x580bba48 (???)
--284860-- REDIR: 0x401b700 (ld-linux-aarch64.so.1:index) redirected to
0x580bba1c (???)
--284860-- Reading syms from
/usr/libexec/valgrind/vgpreload_core-arm64-linux.so
--284860-- object doesn't have a symbol table
--284860-- Reading syms from
/usr/libexec/valgrind/vgpreload_memcheck-arm64-linux.so
--284860-- object doesn't have a symbol table
--284860-- Reading syms from /usr/lib/aarch64-linux-gnu/libhwy_contrib.so.1.0.7
--284860-- object doesn't have a symbol table
--284860-- 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:
==284860== at 0x58040D44: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x58040E93: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x58040FFB: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x580C3BB7: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x580C3D53: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x580C91E3: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5807A497: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5806F613: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5809E927: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x580AB983: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5809AA1B: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5809647F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x5809882F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0x580DFC5F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==284860== by 0xFFFFFFFFFFFFFFFF: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 222 (lwpid 284860)
==284860== at 0x401AB6C: __mmap64 (mmap64.c:58)
==284860== by 0x401AB6C: mmap (mmap64.c:46)
==284860== by 0x40066F3: _dl_map_segments (dl-map-segments.h:139)
==284860== by 0x40066F3: _dl_map_object_from_fd (dl-load.c:1268)
==284860== by 0x40078BF: _dl_map_object (dl-load.c:2272)
==284860== by 0x400243B: openaux (dl-deps.c:64)
==284860== by 0x40012FB: _dl_catch_exception (dl-catch.c:237)
==284860== by 0x40028EB: _dl_map_object_deps (dl-deps.c:232)
==284860== by 0x4017A47: dl_main (rtld.c:1972)
==284860== by 0x4014E8B: _dl_sysdep_start (dl-sysdep.c:140)
==284860== by 0x4016273: _dl_start_final (rtld.c:497)
==284860== by 0x4016273: _dl_start (rtld.c:584)
==284860== by 0x401A193: (below main) (dl-start.S:30)
client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFEFFF150
valgrind stack range: [0x1002CB8000 0x1002DB7FFF] 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.
where:
malat@amdahl ~/pr110643 % dpkg -S
/usr/lib/aarch64-linux-gnu/libhwy_contrib.so.1.0.7
libhwy1:arm64: /usr/lib/aarch64-linux-gnu/libhwy_contrib.so.1.0.7
malat@amdahl ~/pr110643 % apt-cache policy libhwy1:arm64
libhwy1:
Installed: 1.0.7-7
Candidate: 1.0.7-7
Version table:
*** 1.0.7-7 500
500 https://deb.debian.org/debian sid/main arm64 Packages
100 /var/lib/dpkg/status
--
You are receiving this mail because:
You are watching all bug changes.
