[issue5091] Segfault in PyObject_Malloc(), address out of bounds
Charles-Francois Natali
report at bugs.python.org
Sat Mar 5 12:02:31 CET 2011
Charles-Francois Natali <neologix at free.fr> added the comment:
Do you have a coredump ?
It'd be curious to see this faulting address.
I didn't notice the first time, but in the OP case the address is definitely wrong: 0xecc778b7 is above PAGE_OFFSET (0xc0000000 on x86), so unless he's using a kernel with a 4G/4G split (and it's not the case since it seems to be a PAE kernel), it's definitely an invalid/corrupt address...
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5091>
_______________________________________
More information about the Python-bugs-list
mailing list