Skip to content
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 g.shortest_path_tree() in graph.c, line 355 #16

Open
msoulier opened this issue May 4, 2010 · 0 comments
Open

segfault on g.shortest_path_tree() in graph.c, line 355 #16

msoulier opened this issue May 4, 2010 · 0 comments

Comments

@msoulier
Copy link

msoulier commented May 4, 2010

Rebasing to the latest graphserver code has been very bumpy. I am at commit

commit da19ba353f6c17beeec6197a56d183d66d5cb63e
Merge: 95cf72e e337760
Author: Brandon Martin-Anderson 
Date:   Fri Mar 26 11:48:12 2010 -0700

    Merge branch 'master' of [email protected]:bmander/graphserver

And now when I load a graphdb and try to find the shortest_path_tree, I get this segfault

Core was generated by `python ./gs_server.py --gtfsdb=toronto.gtfsdb --graphdb=toronto.gdb --debug'.
Program terminated with signal 11, Segmentation fault.
#0  vGetIncomingEdgeList (g=0x20e2da70, origin_label=0xa0b4944 "sta-10491") at graph.c:355
355         return this->incoming->next; //the first node is a dummy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant