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 when importing local module that imports numba #6717
Comments
I vaguely recall seeing something related to Symengine and Numba not being too compatible. I'll post here as soon as I find it again. |
Is symengine dynamically linked against another llvm compiled without symbol renaming? |
I found it: numba/llvmlite#587 |
the stack traces appear suspiciously similar. |
Should be fixed now with the latest wheels. SymEngine was statically linking to llvm, but was exporting the symbols before. |
@QuantuMope can you confirm? |
Problem is now fixed! Tested on symengine 0.7.0 and numba 0.53.0. |
@QuantuMope thank you for following up and confirming that your issue has been solved. |
@isuruf do you have a link to the symengine patch to hide the symbols? |
https://github.com/symengine/symengine/blob/master/symengine/CMakeLists.txt#L253-L260 (If is for Linux and elseif is for macOS) |
thank you! |
I keep getting segfaults when importing a local module that contains numba into a file that has symengine imported into it.
The segfaults are resolved whenever I remove either one of the imports. Anyone know why this is happening?
I'm using numba 0.53.0 and python 3.8.5 on ubuntu 20.04.
I've also been able to reproduce this on numba 0.52.0 and python 3.6.9 on ubuntu 16.04.
To reproduce, create two files as follow
main.py
utils.py
Then
produces the following:
The text was updated successfully, but these errors were encountered: