Stuart Henderson <[email protected]> writes: > This disables PROT_EXEC mappings in libffi (and thus python). > I'm running with it in a bulk build with the "mandatory W^X" > printfs that are going into snapshots and haven't triggered > them yet, building python itself (done 2.7 and 3.4 so far) > or in the ~200 py-* and py3-* things that have built already > (I would have had a whole stack by now otherwise). > > There are a lot of test failures when this diff is used. > Can anyone figure out if they're anything to worry about?
I only took a quick look, but it looks like closures don't work at all. While I admit that this W|X situation sucks, I think we should still be able to switch back to using them, should the runtime breakage be unfixable in consumer ports. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
