-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
osrm-extract PANIC: unprotected error in call to Lua API (attempt to index a nil value) #694
Comments
How about posting a log of the actual error messages? |
Ok, no problem. I am happy to run more tests if you think this would help.
|
Which profile are you using? A custom one? |
Project-OSRM in the above log is a unaltered clone of the git repository, at master (ef1d75d). What I posted above was using profile.lua, but I get the same result with profiles/car.lua. Interestingly, running the command repeatedly, leads to differing results (differing number of PANIC's):
|
try executing osrm-extract from the Project-OSRM directory. |
Gives the same results.
|
Try if you get same results on develop branch. |
I do. I also tried installing the libluajit-5.1-dev package, which leads to a different error (on the develop branch):
|
I also have this problem with the extractor on Debian Testing.
The strange thing is: I get the same error regardless of the parameters, as long as there is a “file name” given. So it seems it may be a problem with Lua itself. |
Is it possible that one of you could give me access to your machines, so I can have a direct look at stuff? Public keys are at https://github.com/DennisOSRM.keys |
hi all, i have exactly the same probleme on debian wheezy. have you find a solution ? |
See #466 |
Is there something new in Debian or OSRM? I don't think this is related to #466. |
When I attempt to run the extractor, I get one or more of the above error message. I was testing on a clean installation of Debian Testing, with both v0.3.4 and master. The build log can be found here: http://paste.debian.net/23627/
The text was updated successfully, but these errors were encountered: