-
Notifications
You must be signed in to change notification settings - Fork 190
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 on Windows due to PyCall #327
Comments
Could this be related: http://www.ni.gsu.edu/~rclewley/PyDSTool/GettingStarted.html
From the command line you can see that it works already though... |
Did a test and this "segfault every time" at the same line occurs on Mac. It seems that Linux tends to segfault more around the lines that these two OS' segfault every time, indicating that this issue may be related to #328 |
Even with the change from the other thread. Windows still segfaults:
|
I ran this in using PyDSTool, PyCall
dsargs = ds[:args]() |
Closing this because I think it's a duplicate of #328 . Not sure why Mac/Windows deterministically segfault though, while Linux (CentOS) is non-deterministic. |
I am writing a wrapper for PyDSTool and the test code can be found here. I made a special install path to get it installed on Windows and when I do
I get
C:\Users\Chris\.julia\v0.6\Conda\deps\usr\python
, so I check in the terminal:That the Python setup in Windows works. I know that the PyCall wrapper code works (tested on Linux). However, when I try that same code on Windows through PyCall, I get a segfault at the first usage of PyDSTool (exported as
ds
) with the command:DSargs = ds.args()
. The message is as follows:The text was updated successfully, but these errors were encountered: