-
Notifications
You must be signed in to change notification settings - Fork 129
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
odom node crashes with buffer overrun #75
Comments
Hi @tnr00071 -- Try running gdb in RelWithDebInfo, i.e. put |
Hey @kennyjchen Thanks for the suggestion. I ran gdb with RelWithDebInfo and suppressed the output to stdout. This is the backtrace from gdb:
It appears the issue happens at line 427 of odom.cc: I commented this line out and the issue stopped happening. Not sure what causes this line throws the exception ... maybe not locked properly. Could you also update the README.md to include a description of all of the different published topics? Would be nice to know the difference between kf_pose and pose, deskewed and kf_cloud etc. |
@kennyjchen anymore thoughts? |
Hmm, how long after running DLIO is this occurring? It's possible that, after a long time, there are too many keyframes to publish and it subsequently crashes when trying to serialize it (hence the error). For the most part, a lot of the topics being published are for visualization purposes, which can be commented out if you're in a production environment. I'll try to find some time in the future to update the README to include a description of the published topics, as you suggested. I appreciate the feedback! |
Around an hour long data set with an OS1-128 for context. Thanks for the reply! |
Been also trying to run with gdb, to get the exact line that throw the error, but its extremely slow. Will keep trying to debug. Currently running on ros noetic on ubuntu 20.04
The text was updated successfully, but these errors were encountered: