Hello,
I found this one interesting and tried to reproduce it,
and hit this issue quite reliable with an unstable armel chroot,
inside an armhf unstable qemu VM,
or with a Android/LineageOS with real arm CPU.
Unfortunately valgrind is no longer built for armel, and a local armel rebuild
shows
Hi Andrey,
on my aarch64 Raspberry Pi 4, I can successfully build the armel
package.
How can I find a way to reproduce that memory error? Maybe I should
remove the fft const test.
Thanks for the help.
--
Matteo Bini
Control: forwarded -1 https://github.com/alexkay/spek/issues/308
Source: spek
Version: 0.8.5+dfsg-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=spek=armel=0.8.5%2Bdfsg-3%2Bb3=1711383117=0
fft const
double free or corruption (!prev)
/bin/bash: line 6: 27223 Aborted ${dir}$tst
FAIL: test
-- System Information:
4 matches
Mail list logo