This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author berker.peksag
Recipients amaury.forgeotdarc, belopolsky, berker.peksag, bivab, doko, fijall, meador.inge, vstinner
Date 2016-03-02.06:11:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456899082.6.0.155380329325.issue17580@psf.upfronthosting.co.za>
In-reply-to
Content
> Which patch?

Looks like the patch can be found at https://github.com/atgreen/libffi/pull/34/ and it has been released in libffi 3.1: https://github.com/atgreen/libffi/blob/17ffc3655a531c116e9eb9cc933e50bb1e5c47f8/ChangeLog.libffi-3.1#L481

(It's hard to share a specific commit since libffi's history is not linear.)

The patch also has been merged into CPython's fork in 0fef0afb9d19 (Update the ctypes module's libffi to v3.1):

* https://github.com/python/cpython/blob/master/Modules/_ctypes/libffi/src/arm/ffi.c#L43
* https://github.com/python/cpython/blob/master/Modules/_ctypes/libffi/src/arm/ffi.c#L128

I don't have an ARM system to run David's reproducer (thanks for your report and for the test script, by the way!), but I think we can safely assume that this has already been fixed.
History
Date User Action Args
2016-03-02 06:11:22berker.peksagsetrecipients: + berker.peksag, doko, amaury.forgeotdarc, belopolsky, vstinner, meador.inge, fijall, bivab
2016-03-02 06:11:22berker.peksagsetmessageid: <1456899082.6.0.155380329325.issue17580@psf.upfronthosting.co.za>
2016-03-02 06:11:22berker.peksaglinkissue17580 messages
2016-03-02 06:11:22berker.peksagcreate