Kees Cook added the comment:
The stack protector will add 8 (aligned, so possibly padded) bytes to each
stack frame of functions with arrays of 8 or greater bytes. So if things are
marginal, this could make the difference between Pythons compiled with/without
-fstack-protector.
N.B. if
Kees Cook added the comment:
So, digging a little further, I think this is a now-fixed kernel bug with stack
growth. There were known issues prior to Sep 2009 with 64bit stack growth with
ASLR, which is enabled by default. Upstream fix:
http://git.kernel.org/?p=linux/kernel/git/torvalds
