Timeline for Set executable heap
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2020 at 8:12 | comment | added | grandchild | This doesn't seem to be true in 2020, on a 5.8.7 kernel -- compiling the example program does indeed result in a SIGSEV/segfault these days. mprotect doesn't seem to do much. Still trying to figure out why... | |
| Nov 27, 2013 at 20:50 | comment | added | wingedsubmariner | I don't think the old architectures would behave that way, the underlying hardware has no way of knowing what memory pages are mmap'ed executable files and which are meant for heap space, unless it is told. Architectures that don't support something like the no-execute flag on pages will always have executable heap, for others, the kernel is the only limitation. | |
| Dec 6, 2011 at 17:28 | history | answered | user732 | CC BY-SA 3.0 |