Bug#1061496: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check

Hi Petter, On 2024-02-10 06:04, Petter Reinholdtsen wrote: > This issue cause a failing autopkgtest with libvorbis. I would much > prefer a fix in valgrind instead of disabling a autopkgtest check. As an alternative to disabling the test, you could consider disabling stack-clash-protection on

Bug#1061496: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check

Control: affects -1 + libvorbis-dev Control: block 1061501 by -1 This issue cause a failing autopkgtest with libvorbis. I would much prefer a fix in valgrind instead of disabling a autopkgtest check. -- Happy hacking Petter Reinholdtsen

Bug#1061496: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check

Package: valgrind Version: 1:3.20.0-2.1 Severity: important User: debian-...@lists.debian.org Usertags: 32bit-stackclash Tags: upstream On armhf, valgrind dies with a SIGSEGV when checking certain programs built with either -fstack-clash-protection or -fstack-check. The following example is a