[pypy-dev] Looking for clues to consistent Seg Fault in PyPy 2.6.1

Amaury Forgeot d'Arc amauryfa at gmail.com
Mon Oct 12 11:24:00 CEST 2015


2015-10-12 11:10 GMT+02:00 Armin Rigo <arigo at tunes.org>:

> Hi Jeff,
>
> Ah, I think I understand now what is going on.  The special-casing for
> PyPy should not be needed at all, but when I removed it, I get
> assertion failures.  Now I get the reason---yes, it is yet another bug
> inside cpyext, caused by yet another access pattern of "PyObject *"
> that is somehow unusual but should be allowed.
>
> I can try to fix it inside cpyext, and then the "if IS_PYPY" cases in
> proxy.pxi should be removed.  (I'm unsure if it is easy to change them
> to "if the version of PyPy is <= 2.6.1"...)
>

We define it as a string (in pypy/module/cpyext/include/patchlevel.h)
#define PYPY_VERSION "2.6.0-alpha0"

-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20151012/f51680b7/attachment.html>


More information about the pypy-dev mailing list