-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault using mpz on OSX #350
Comments
I've released gmpy2 2.1.3 and it is a more recent build. Can you try testing it? |
I get an import error. Also tried to force a re-install and confirmed that it's 2.1.3.:
|
There was an error in the build process. I've upload 2.1.4. Can you try it? |
I just updated to 2.1.4 and the issue is still there. Sorry. Please let me know if there is anything I can do to provide you with more information to pinpoint / solve this. |
I've made another update to the build process. I don't have a machine I can use to test the binary wheels. Can you test the build? A zip file containing all four versions is at https://github.com/aleaxit/gmpy/suites/9929671653/artifacts/480553600 After extracting the appropriate file, you should be able to install it manually using pip3 install --upgrade --force-reinstall gmpy2-2.1.4-cp310-cp310-macosx_11_0_arm64.whl |
Kudos! You nailed it! Ran it several times, even with higher limits. No segmentation faults anymore. Well done! Case closed! 🎉 |
I get a segmentation fault on OSX using my MacBook Pro M1, using a Python program for calculating a factorial and a modulo.
Used versions of Python, gmpy2 and OSX:
Python program:
This program gives every time a Segmentation Fault (
[1] 33487 segmentation fault python3 ./gmpy2_factorial.py
), but at different progress of the program (e.g.: each time after a different number of iterations).I tried the same program on another platform (tio.run, Debian on amd64) without problems. So it seems to be specific for OSX and/or the M1 hardware. A bit more details for my platform:
The text was updated successfully, but these errors were encountered: