-
-
Notifications
You must be signed in to change notification settings - Fork 393
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] Graph.pagerank() #636
Comments
Also works on Ubuntu Linux where igraph is compiled with |
I've got this problem too on Ubuntu 14.04 (python3, python-igraph0.7) |
Is there any further useful information I could provide? |
Finally managed to reproduce the issue in an Ubuntu VM. I'll keep this issue updated as I make progress. |
Found a workaround (although the cause is still not clear): just call |
Thank you! That works for me. |
Got the same symptoms using two different environments: Ubuntu 14.04 and OS X 10.9, both with python (3.4.0 / 3.4.1), python-igraph==0.7 and igraph 0.7.1. |
Fun fact: this does not happen when using the debug build of Python on Ubuntu, only with the release build. |
Okay, this is fixed in the development branch now; see the patch above. |
For the record: the problem was that the |
Why was this closed? There is still a segfault on |
I tend to close issues after the fix has been committed and not after releases. However, development has stalled on python-igraph as I don't have time for it any more so there was no new release since the fix was committed. Your best bet right now is to compile the Python interface from source instead. |
For igraph, from the current master I am able to make a release tarball (after some changes in |
Sorry, it's not that easy, but I wanted to let you know that it seems like igraph's development will hopefully gain some momentum; we aim for a proper 0.8.0 release next month. |
Arch Linux 3.15.1
Python 2.7.7
igraph 0.7.1
python-igraph 0.7.0
Consistently crashes with an error message like the following:
Everything else works. The same code runs fine on OS X. Perhaps something is being interpreted differently between
gcc
andclang
?The text was updated successfully, but these errors were encountered: