-
Notifications
You must be signed in to change notification settings - Fork 43
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
Receiver node from "develop" branch dies due to accessing nullptr #17
Comments
This could potentially trigger a segfault when all messages are older than 5s. Maybe related: #17
Hey, thanks for the report! I think you uncovered a pretty serious bug - I'm not sure how this went unnoticed for so long :/ I'm pretty sure it's not a concurrency issue, since But there's a bug hidden in Could you please try the fix in #18? |
This could potentially trigger a segfault when all messages are older than 5s. Maybe related: AIS-Bonn#17
@xqms thanks for your quick reply and fix ... amazing! I did try the proposed fix a few times and could not reproduce the error anymore. I'm gonna try again next week with more extensive tests and let you know. Once again, thanks a lot for the fix! |
Hi @xqms Unfortunately the issue happens again even after using the proposed fix. I got another backtrack:
FYI @tomlankhorst |
That's unfortunate... Could you please compile nimbro_network in |
Hi @xqms
We've got an issue with the receiver node dying because of segfault (exit code
-11
) when using the "develop" branch.@tomlankhorst and I tried to debug this issue and could get a backtrace using
gdb
(see end of the message). We were wondering if you could provide us with your feedback about this issue. This is our setup:When the agent goes out of connection range and comes back after some minutes, we often get the receiver node dying on the base station. We suspect that
Depacketizer::addPacket
is called asynchronously on the same object (for example when 2 UDP packets are received) and soaddPacket
is called twice. But if it's called async, then it will mess up because the value of the iterator will be changing.Do you have any hint or suggest on how we could fix this issue?
Best,
Marco
Backtrace:
The text was updated successfully, but these errors were encountered: