debugging gsasl autopkg test error on armhf

[Emanuele Rocca]

Hi Andreas!

On 2023-12-03 06:20, Andreas Metzler wrote:
> gnutls28 is currently blocked from testing because gsasl's autopkg test
> fails.

We recently enabled stack-clash-protection on all arm ports. On 32 bit
arm the feature is implemented using stack probes, which valgrind flags
as illegal accesses because they occur below the stack pointer address.
However, stack probes don't actually care about the contents - just that
the address is valid.

When it comes to armel, valgrind is not supported altogether.

I have added a suppression to valgrind 1:3.20.0-2 on armhf, which has
now migrated to testing. gsasl tests pass on all arm ports (but fail on
i386): https://ci.debian.net/packages/g/gsasl/

The i386 failures are mostly due to the valgrind checks "Conditional
jump or move depends on uninitialised value(s)". They did pass however
with gsasl 2.2.0-1, which does not seem to have significant differences
with 2.2.0-2 at first glance. The big one is that 2.2.0-1 was built with
GCC 12, while 2.2.0-2 with GCC 13. Checking if the failures can be
reproduced with GCC 12 may be worth a shot.

  Emanuele