-
Notifications
You must be signed in to change notification settings - Fork 425
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
Another crash related to transports #30
Comments
Or maybe it's related to #29 anyway;
|
It handles domain this way intentionally, the reason of it, resolver might work too long. Later one I will add proper implementation, but exclude such addresses for now. |
Ok, not a bug then :) |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found another crash that seems related to transports, but does not seem to be in relation to #29 (gdb backtrace at bottom)
Any clues?
Another note (not related): Seems like if an routerInfo contains a domain instead of an IP, i2pd will get an unexpected address, but this does not crash it.
The text was updated successfully, but these errors were encountered: