-
Notifications
You must be signed in to change notification settings - Fork 27
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
Initialization order fiasco in some data #71
Comments
@oxidase this doesnt look too bad. ill clean it up. maybe its a good time to switch prime_server over to a third party dependency in valhalla. i presume it will eventually be removed in favor of just running valhalla under a node express app? |
@kevinkreiser it is a minor issue and occurs for very specific conditions. Just want to make it visible if someone hits the same problem. |
I hope that you will keep ability to run valhalla without node. I am using it as a server on mobile platform that doesn't have node support and we'll be hit hard if valhalla will switch off this ability. So, please keep prime_server either separate or third-party, but as available interface for valhalla |
@rinigus i think we can find something that works here. the |
We are bit branching from the original issue, but let me ask a question regarding From the brief look on the methods of |
@rinigus please open an issue in the valhalla repo and I'd be glad to document it further. its basically just if you have a request like:
then you call the actor like:
And that works the same for all of the other apis like matrix and isochrone etc. |
Running valhalla node bindings with enabled address sanitizer and linked with prime_server crashes due to incorrect initialization order of static structures:
and
The first crash is fixed by the patch
The second one is tricky, because exceptions can be initialized before initialization of
vsprintf
internal data.The text was updated successfully, but these errors were encountered: