Mike Hearn mike@theoretic.com writes:
According to the exec-shield paper, its effects can include revealing "bugs in applications that assume PROT_READ implies PROT_EXEC" due to the funky things it does with relocations into the ASCII-armour. Not sure but it might be worth ensuring mprotect is called afterwards....
mprotect is always called, and anyway the area is allocated with PROT_EXEC already so it shouldn't make any difference.