-
Notifications
You must be signed in to change notification settings - Fork 188
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
Segfault related to PyCall #15
Comments
Actually, I can reproduce this particular error pretty well if I interrupt the same function in the same way. Let me know if you need/want a more specific test case, and I'll see what I can come up with. |
I think the problem is that the Unfortunately, there doesn't seem to be any way to do an atomic @JeffBezanson, can you comment? |
Yes, that would probably fix it. We should probably also expose |
There are additional subtleties in really doing this right. Python would prefer to have its own |
I've been getting random julia segfaults recently. Nothing specifically reproducible, but in this case, it happened at the REPL on the command immediately after I interrupted a PyCall function:
The core dump gives
Perhaps
pycall
needs to be atomic in this case, or something isn't getting cleaned up by my interruption?The text was updated successfully, but these errors were encountered: