https://bugs.kde.org/show_bug.cgi?id=514297
--- Comment #11 from [email protected] --- If this is a way to go then I can imagine adding a new flag (such as maybe hasMG as in madvise guard page) to the NSegment struct in include/pub_tool_aspacemgr.h and working with that. madvise(MADV_GUARD_INSTALL) doesn't change the memory protection flags, so that the existing hasR, hasW, and hasX would continue tracking it in aspacemgr, and so MADV_GUARD_REMOVE would just unset this new flag and client execution would continue? -- You are receiving this mail because: You are watching all bug changes.
