Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT
Hi Paul, On 2024-04-06 11:38, Paul Gevers wrote: > I noticed you "binNMU"-ed siridb-server in Ubuntu where it built > successfully on all arches. In Debian I got the bug below reported. Any idea > what the difference could be between the state of Debian and the state of > Ubuntu that causes this? Unfortunately valgrind on armhf does not work well when checking programs built with stack-clash-protection, see #1061496. Mostly for that reason, Ubuntu decided not to enable stack-clash-protection at all on armhf, while we followed the route of enabling it by default and then either disabling it for programs using valgrind or disabling the valgrind checks on armhf. Given that in this case the code valgrind stumbles on is in a shared library (libpcre2-8) and not in siridb itself, my suggestion would be skipping the valgrind checks by removing armhf from https://sources.debian.org/src/siridb-server/2.0.51-3/debian/control/#L18 FTR I am tracking these problems with a usertag: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org;tag=32bit-stackclash Emanuele
Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT
Hi William, I noticed you "binNMU"-ed siridb-server in Ubuntu where it built successfully on all arches. In Debian I got the bug below reported. Any idea what the difference could be between the state of Debian and the state of Ubuntu that causes this? reproducible-builds [1] confirms that the problem exists in both unstable and testing, introduced somewhere after 2023-11-02. Paul [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/siridb-server.html On 01-04-2024 12:00 a.m., Sebastian Ramacher wrote: Source: siridb-server Version: 2.0.51-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=siridb-server=2.0.51-2%2Bb3=armhf=1711922161 Testing expr␛[32mOK␛[0m (8.519 ms) ==3276877== ==3276877== Process terminating with default action of signal 11 (SIGSEGV) ==3276877== Access not within mapped region at address 0xFEC4F704 ==3276877==at 0x495F6F0: pcre2_compile_8 (in /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2) ==3276877== If you believe this happened as a result of a stack ==3276877== overflow in your program's main thread (unlikely but ==3276877== possible), you can try to increase the size of the ==3276877== main thread stack using the --main-stacksize= flag. ==3276877== The main thread stack size used in this run was 8388608. ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT Cheers OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT
Source: siridb-server Version: 2.0.51-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=siridb-server=2.0.51-2%2Bb3=armhf=1711922161 Testing expr␛[32mOK␛[0m (8.519 ms) ==3276877== ==3276877== Process terminating with default action of signal 11 (SIGSEGV) ==3276877== Access not within mapped region at address 0xFEC4F704 ==3276877==at 0x495F6F0: pcre2_compile_8 (in /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2) ==3276877== If you believe this happened as a result of a stack ==3276877== overflow in your program's main thread (unlikely but ==3276877== possible), you can try to increase the size of the ==3276877== main thread stack using the --main-stacksize= flag. ==3276877== The main thread stack size used in this run was 8388608. ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT Cheers -- Sebastian Ramacher