Open Erotemic opened 8 years ago
Hey. If this is a bug in the cython code, this is the right repo (what other versions are there?). If it is a bug in gco, it is not, and you should write to the original authors. I don't have a bunch of time to investigate this right now. Have you tried debugging it with gdb?
(I'm not sure if this is the correct repo to submit this issue. There seem to be 3 versions of the rpo out there, and I don't see an original repo for GCO itself)
I've found a specific set of inputs that causes a segfault in pygco.cut_from_graph.
I wrote a script to demonstrate this and attempt to work down the case to a minimal cause. Unfortunately I've been unable to identify the cause.
However, I did find one (unrelated) easy to fix segfault that happens when you specify an edge index that is out of bounds. This is also in the test script.
The script defines a function for each test case, and then runs them in the main part. There are several tests for what I thought might be causing the issue, but those ideas turn out to be wrong.
The final test is the smallest version of the error I could reproduce. In this test, removing any of the edges suppresses the error. Then when running with all edges the segfault occurs.