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&ver=2.0.51-2%2Bb3&arch=armhf&stamp=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
