[pypy-issue] [issue1020] segfault when running test_greenlet.py through pypy pytest.py

[Justin Patrin]

Justin Patrin <papercrane at reversefold.com> added the comment:

Not sure if this is the same segfault but if I try to run my jevent both.py 
example (see Issue #1016 for tarball) through py.py now that the --continuation 
error is fixed (thanks fijal) I also get a crash.

PYTHONPATH=. python ~/src/pypy/pypy/bin/py.py --allworkingmodules -v 
examples/both.py

The output ends with:
[platform:execute] gcc -dynamiclib -undefined dynamic_lookup 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_9.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_10.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_11.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_12.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_13.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_14.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_15.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_16.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_17.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_18.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_19.o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/module_cache/module_20.o -arch x86_64 -Wl,-
exported_symbols_list,/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-
default-48/dynamic-symbols-6 -lssl -lcrypto -o 
/var/folders/qv/4vbv0p790d15tdmtlmncmsnr0000gq/T/usession-default-
48/shared_cache/externmod_2.dylib
Python(58429) malloc: *** error for object 0x7f950c30b6f8: incorrect checksum 
for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug

----------
status: unread -> chatting

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue1020>
________________________________________