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
