https://bugs.kde.org/show_bug.cgi?id=511717
Mark Wielaard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #38 from Mark Wielaard <[email protected]> --- (In reply to Philippe Waroquiers from comment #37) > We discussed this proposal on IRC and agreed to push and backport as a > (likely ? hopefully ?) temporary solution > waiting for a possibly cleaner approach in the adress space manager. Filed https://bugs.kde.org/show_bug.cgi?id=514297 for tracking this in the address space manager. Pushed this as a workaround for now (including a NEWS entry explaining why). commit 19a34d1d9376f459cf0a19feb39ea4ab27690390 Author: Mark Wielaard <[email protected]> Date: Wed Jan 7 22:20:49 2026 +0100 Disable linux madvise MADV_GUARD_INSTALL 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 -- You are receiving this mail because: You are watching all bug changes.
