Summary: | armh: Memcheck and even Nulgrind get signal 11 in _dl_start | ||
---|---|---|---|
Product: | Sisyphus | Reporter: | Vitaly Chikunov <vt> |
Component: | valgrind | Assignee: | Ivan A. Melnikov <iv> |
Status: | NEW --- | QA Contact: | qa-sisyphus |
Severity: | normal | ||
Priority: | P5 | CC: | iv |
Version: | unstable | ||
Hardware: | x86 | ||
OS: | Linux |
Description
Vitaly Chikunov
2022-08-09 01:15:15 MSK
Certainly not, since there was build failure (which is resolved) and here is usage failure (which is still present). My opinion: If valgrind is impossible to work on armh, perhaps it should not be built there. Googling. Looks similar to this unreplaced and unresolved upstream bug: "Valgrind crashes with segmentation fault and a lot invalid writes on Raspberry Pi 4B" on Archlinux: https://bugs.kde.org/show_bug.cgi?id=452575 (In reply to Vitaly Chikunov from comment #2) > My opinion: If valgrind is impossible to work on armh, perhaps it should not > be built there. I thought that IF valgrind does not support arm32 at all, but now I think valgrind SHOULD work on armh. I tested in docker on arm32v7/ubuntu:jammy and it's worked. ==8436== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info --8441:1: machine ARMv7 VFP 1 VFP2 1 VFP3 1 NEON 1 --8441:1: main ... arch = ARM, hwcaps = ARMv7-neon-vfp --8441:2:launcher selected platform 'arm-linux' I tested in docker on arm32v7/fedora (which is f35) and it's working. ==285== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info --293:1: machine ARMv7 VFP 1 VFP2 1 VFP3 1 NEON 1 --293:1: main ... arch = ARM, hwcaps = ARMv7-neon-vfp --293:1:launcher selected platform 'arm-linux' arm32v7/ubuntu:bionic worked ok. ==1443== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info arm32v7/alt:sisyphus Segmentation fault (core dumped) ==96== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info --100:1: machine ARMv7 VFP 1 VFP2 1 VFP3 1 NEON 1 --100:1: main ... arch = ARM, hwcaps = ARMv7-neon-vfp arm32v7/ubuntu:focal worked ok. ==1520== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info arm32v7/ubuntu:jammy worked ok. ==8431== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info Apparently nobody wants to invest their time into making valgrind work on armv7 in Sisyphus, according to #40446. Maybe latest version have it miraculously fixed? 1 year is passed since than. > 1 year is passed since than.
I meant, since 3.17.0 that we have.
|