Bug 514297 - Track madvise MADV_GUARD_INSTALL in address space manager
Summary: Track madvise MADV_GUARD_INSTALL in address space manager
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.25 GIT
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-07 21:18 UTC by Mark Wielaard
Modified: 2026-01-07 21:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2026-01-07 21:18:33 UTC 
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.
See https://bugs.kde.org/show_bug.cgi?id=511717

It would be better to track madvise MADV_GUARD_INSTALL using the address space manager.