[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #7 from Mathieu Malaterre --- (In reply to Mark Wielaard from comment #4) > Thanks, so that is in libhwy_contrib.so.1.0.7 which is > https://packages.debian.org/sid/libhwy1 and can be downloaded through > http://ftp.debian.org/debian/pool/main/h/highway/libhwy1_1.0.7-7_arm64.deb > > Without an arm64 debian setup trying to unpack that and looking for the any > DW_CFA expressions with suspecious DW_OP expressions might be helpful. Just fyi % curl -O http://ftp.debian.org/debian/pool/main/h/highway/libhwy1_1.0.7-7_arm64.deb % ar x libhwy1_1.0.7-7_arm64.deb % tar tvf data.tar.xz [...] -rw-r--r-- root/root 2295800 2023-09-15 11:47 ./usr/lib/aarch64-linux-gnu/libhwy_contrib.so.1.0.7 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #6 from Mathieu Malaterre --- Created attachment 161747 --> https://bugs.kde.org/attachment.cgi?id=161747=edit % valgrind --debug-dump=frames ./fails >& /tmp/frames.txt -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #3 from Mathieu Malaterre --- (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 0x: ??? 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)
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074
Mathieu Malaterre changed:
What|Removed |Added
CC||ma...@debian.org
--- Comment #1 from Mathieu Malaterre ---
Same with highway:
% clang++-16 -o fails math_test4.cc -lhwy_contrib
% cat math_test4.cc
int main() {}
% clang++-16 -o fails math_test4.cc -lhwy_contrib
% valgrind ./fails
==3733364== Memcheck, a memory error detector
==3733364== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==3733364== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==3733364== Command: ./fails
==3733364==
--3733364-- 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:
==3733364==at 0x58040D44: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x58040E93: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x58040FFB: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x580C3BB7: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x580C3D53: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x580C91E3: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5807A497: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5806F613: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5809E927: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x580AB983: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5809AA1B: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5809647F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x5809882F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x580DFC5F: ??? (in
/usr/libexec/valgrind/memcheck-arm64-linux)
==3733364==by 0x: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 222 (lwpid 3733364)
==3733364==at 0x401AB6C: __mmap64 (mmap64.c:58)
==3733364==by 0x401AB6C: mmap (mmap64.c:46)
==3733364==by 0x40066F3: _dl_map_segments (dl-map-segments.h:139)
==3733364==by 0x40066F3: _dl_map_object_from_fd (dl-load.c:1268)
==3733364==by 0x40078BF: _dl_map_object (dl-load.c:2272)
==3733364==by 0x400243B: openaux (dl-deps.c:64)
==3733364==by 0x40012FB: _dl_catch_exception (dl-catch.c:237)
==3733364==by 0x40028EB: _dl_map_object_deps (dl-deps.c:232)
==3733364==by 0x4017A47: dl_main (rtld.c:1972)
==3733364==by 0x4014E8B: _dl_sysdep_start (dl-sysdep.c:140)
==3733364==by 0x4016273: _dl_start_final (rtld.c:497)
==3733364==by 0x4016273: _dl_start (rtld.c:584)
==3733364==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.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 248998] ARMv5 and v6 support
https://bugs.kde.org/show_bug.cgi?id=248998 Mathieu Malaterre changed: What|Removed |Added CC||ma...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Mathieu Malaterre changed: What|Removed |Added Summary|Valgrind should not |Valgrind should not require |required neon (simd) on |neon (simd) on armhf |armhf | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 --- Comment #2 from Mathieu Malaterre --- Correction, the actual patch should be: sed -i -e 's/cortex-a8/generic-armv7-a/g' Makefile.all.am There's no need for the fpu selection to be specified as generic-armv7-a defaults to vfpv3-d16. Credits: Richard Earnshaw https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928224#60 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Mathieu Malaterre changed: What|Removed |Added URL||https://bugs.debian.org/cgi ||-bin/bugreport.cgi?bug=1014 ||091#12 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Mathieu Malaterre changed: What|Removed |Added Latest Commit||022dfeee73726d92ecc0349ebe4 ||2d7b52132b8e5 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 --- Comment #1 from Mathieu Malaterre --- Here is a suggested patch: % sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] New: Valgrind should not required neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Bug ID: 456200 Summary: Valgrind should not required neon (simd) on armhf Product: valgrind Version: 3.20 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: ma...@debian.org Target Milestone: --- SUMMARY valgrind is currently configured to build with: -mcpu=cortex-a8 Since gcc-11 (and above) this means the compiler is free to include simd (neon) instruction. Since neon is not stricly required to run valgrind on armhf, please reduce requirement. STEPS TO REPRODUCE % git clone % ./autogen.sh && ./configure && make % ./vg-in-place Illegal instruction. OBSERVED RESULT neon instructions is present in the binaries. Program received signal SIGILL, Illegal instruction. vgPlain_am_startup (sp_at_startup=3204445696) at m_aspacemgr/aspacemgr-linux.c:1626 1626 init_nsegment(); (gdb) x/i $pc => 0x58071090 : vmov.i32d16, #0 ; 0x EXPECTED RESULT valgrind should run on neon-less armhf. SOFTWARE/OS VERSIONS % cat /proc/cpuinfo model name : ARMv7 Processor rev 2 (v7l) Features: half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt vfpd32 lpae ADDITIONAL INFORMATION Complete thread on valgrind-users https://sourceforge.net/p/valgrind/mailman/valgrind-users/thread/CA%2B7wUsyP0aTmfQMi3ro0AeXvRW8v2G1UYsLoFxpvi_RCUrbdJQ%40mail.gmail.com/#msg37673816 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361405] disInstr(ppc): unhandled instruction: 0xFF81010C
https://bugs.kde.org/show_bug.cgi?id=361405 Mathieu Malaterre changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Mathieu Malaterre --- I cannot remember what I was doing back then. Closing as fixed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361405] disInstr(ppc): unhandled instruction: 0xFF81010C
https://bugs.kde.org/show_bug.cgi?id=361405 --- Comment #2 from Mathieu Malaterre <ma...@debian.org> --- This is a 32bit process -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361405] New: disInstr(ppc): unhandled instruction: 0xFF81010C
https://bugs.kde.org/show_bug.cgi?id=361405 Bug ID: 361405 Summary: disInstr(ppc): unhandled instruction: 0xFF81010C Product: valgrind Version: 3.11.0 Platform: Debian unstable OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: ma...@debian.org Seems like valgrind is missing support for PowerPC: dis_fp_scr(ppc)(instr,mtfsfi) disInstr(ppc): unhandled instruction: 0xFF81010C primary 63(0x3F), secondary 268(0x10C) ==29681== valgrind: Unrecognised instruction at address 0xfead320. ==29681==at 0xFEAD320: __slow_ieee754_sqrt (in /lib/powerpc-linux-gnu/libm-2.22.so) ==29681==by 0xFEA7413: __hypot_finite (in /lib/powerpc-linux-gnu/libm-2.22.so) ==29681==by 0xFEB9187: hypot (in /lib/powerpc-linux-gnu/libm-2.22.so) ==29681==by 0xFEBAEFF: cabs (in /lib/powerpc-linux-gnu/libm-2.22.so) ==29681==by 0x1019BA2B: hill_climbing_update (threadpool-ms.c:1165) ==29681==by 0x1019BA2B: heuristic_adjust (threadpool-ms.c:1296) ==29681==by 0x1019EFE3: ves_icall_System_Threading_ThreadPool_NotifyWorkItemComplete (threadpool-ms.c:1573) ==29681==by 0x46AFC8B: ??? ==29681==by 0x46A465B: ??? ==29681==by 0x46A4233: ??? ==29681==by 0x46A42E7: ??? ==29681==by 0x1002633B: mono_jit_runtime_invoke (mini-runtime.c:2691) ==29681==by 0x101C55E3: do_runtime_invoke (object.c:2898) ==29681== Your program just tried to execute an instruction that Valgrind ==29681== did not recognise. There are two possible reasons for this. ==29681== 1. Your program has a bug and erroneously jumped to a non-code ==29681==location. If you are running Memcheck and you just saw a ==29681==warning about a bad jump, it's probably your program's fault. ==29681== 2. The instruction is legitimate but Valgrind doesn't handle it, ==29681==i.e. it's Valgrind's fault. If you think this is the case or ==29681==you are not sure, please let us know and we'll try to fix it. ==29681== Either way, Valgrind will now raise a SIGILL signal which will ==29681== probably kill your program. ==29681== Thread 7 Threadpool work: ==29681== Invalid write of size 4 ==29681==at 0x100E6658: handle_signal_exception (exceptions-ppc.c:717) ==29681==by 0xFEAD31F: __slow_ieee754_sqrt (in /lib/powerpc-linux-gnu/libm-2.22.so) ==29681== Address 0x813e6b4 is on thread 7's stack ==29681== Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
