mirror of
git://sourceware.org/git/valgrind.git
synced 2026-01-12 00:19:31 +08:00
19a34d1d93
glibc 2.42+ (with linux 6.13+) uses MADV_GUARD_INSTALL to setup stack guard pages. valgrind currently isn't able to track this and such guard pages also don't show up in /proc maps (only in /proc pagemap since linux 6.14). For now valgrind fails a madvise MADV_GUARD_INSTALL syscall with EINVAL. This causes glibc to fall back to mprotect PROT_NONE which valgrind is able to track. https://bugs.kde.org/show_bug.cgi?id=511717