[issue34957] Segementation faults on ARM and ARM64

Change by Zachary Ware : -- resolution: works for me -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue34957] Segementation faults on ARM and ARM64

Kubilay Kocak added the comment: All our FreeBSD ports (lang/python??) and the packages produced from them all contain a LIBFFI option which is enabled by default, since 2015 [1][2]: LIBFFI=on: Use libffi from ports instead of bundled version This means that any 'default' package builds of t

[issue34957] Segementation faults on ARM and ARM64

Zachary Ware added the comment: IIRC, the default in 3.6 is to use `--with-system-ffi` if available on all platforms but macOS, falling back to the bundled copy only if a system copy can't be found; 3.7 removes the bundled copy. Also, the version bundled with 3.6 is v3.2.1. Note though tha

[issue34957] Segementation faults on ARM and ARM64

STINNER Victor added the comment: > Upgrade to 3.7 fixed the main problem for me, or at least on the > hardware/arch I use. For Python, we should try to identify the required backport, or upgrade libffi in Python 3.6. But I'm scared by Modules/_ctypes/libffi/ since it's unclear to me if we

[issue34957] Segementation faults on ARM and ARM64

Stefan Rink added the comment: Upgrade to 3.7 fixed the main problem for me, or at least on the hardware/arch I use. -- On ARM32 it still failed but I don't have debugging symbols there so not so easy to troubleshoot further -- -- resolution: -> works for me __

[issue34957] Segementation faults on ARM and ARM64

Stefan Rink added the comment: On ARM32 it still crashed but on the ARM64 upgrade to 3.7 helped! Need to do some more testing but it looks like it's working now. # python3.7 Python 3.7.0 (default, Sep 29 2018, 05:58:20) [Clang 6.0.1 (tags/RELEASE_601/final 335540)] on freebsd12 Type "help", "

[issue34957] Segementation faults on ARM and ARM64

Stefan Rink added the comment: * (re)installed libffi but it was already version 3.2.1. * Currently compiling python3.7 on both ARM and AARCH64 to test them. This may take a while because I need to install dask again for 3.7 to test.. Didn't try this on Linux ARM yet so I'll also try that. P

[issue34957] Segementation faults on ARM and ARM64

STINNER Victor added the comment: Is it possible that this bug is a duplicate of bpo-29804? Would you be able to test Python 3.7.1RC1? Sadly, this issue says "OK, PR 1559 (in 3.7.0) for Issue30353 has been backported to 3.6 in PR 5954 for release in 3.6.5". I know that FreeBSD uses our bund

[issue34957] Segementation faults on ARM and ARM64

New submission from Stefan Rink : When trying to run dask distributed on ARM you will end with a segmentation fault on multiple in multiple tests; Works on AMD64 but does not work on ARM or AARCH64 and results in a Signal 11. Example; # python Python 3.6.6 (default, Sep 29 2018, 05:50:41) [G