Re: debugging gsasl autopkg test error on armhf

2023-12-04 Thread Andreas Metzler
On 2023-12-04 Emanuele Rocca wrote: > 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 s

Re: debugging gsasl autopkg test error on armhf

2023-12-04 Thread 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 acce

Re: debugging gsasl autopkg test error on armhf

2023-12-03 Thread Adrien Nader
Hi Andreas, On Sun, Dec 03, 2023, Andreas Metzler wrote: > Hello, > > gnutls28 is currently blocked from testing because gsasl's autopkg test > fails. I have played around on abel: > > Taking a trixie chroot and pulling in newer gnutls via LD_LIBRARY_PATH > makes most of the testsuite fail, incl

Re: debugging gsasl autopkg test error on armhf

2023-12-03 Thread Mate Kukri
Hello, That is the same issue we had in Ubuntu, and is caused by the recent addition of the -fstack-clash-protection compiler flag. There is an earlier thread discussing exactly this on debian-arm. Mate Kukri On 12/3/23 17:20, Andreas Metzler wrote: Hello, gnutls28 is currently blocked fro

debugging gsasl autopkg test error on armhf

2023-12-03 Thread Andreas Metzler
Hello, gnutls28 is currently blocked from testing because gsasl's autopkg test fails. I have played around on abel: Taking a trixie chroot and pulling in newer gnutls via LD_LIBRARY_PATH makes most of the testsuite fail, including this trivial test: 8X-- LD_LIBRARY_PA