The current approach we take with WX memory protection is to run with enabled Write by default and turning Execute as needed.
I think we should also try flipping this around and try running with Execute by default and turning Write as needed.
This would give us a better coverage and flush more codepaths to have greater confidence in our "whack the mole" approach.
I think we should also try flipping this around and try running with Execute by default and turning Write as needed.
This would give us a better coverage and flush more codepaths to have greater confidence in our "whack the mole" approach.
- relates to
-
JDK-8327860 Java processes get killed, leaving no hs_err/stack trace on macOS 14.4
-
- Closed
-
-
JDK-8307817 AARCH64: make macOS W^X locking more fine grained
-
- In Progress
-
-
-
- Resolved
-
-
-
- Closed
-