Fixed monocular-only, stereo-olny and RGB-D segment fault on KITTI and TUM RGBD #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Excellent work! Thank you very much for your contribution to the open source community. 😘 The work of ORB-SLAM series has helped and inspired many researchers and engineers.
I've noticed that segment fault occurred when testing ORB_SLAM3 in monocular-only, or stereo-olny, or RGB-D on KITTI and TUM RGB-D datasets, as issue #3 , #8 , #16 , #18 , #21 mentioned. So I modified .yaml files and codes to fix it.
In addition, I encountered a small error after I compiled the source code of ORB-SLAM3:
After testing, this error only appeared with higher version of GCC/G++ compiler such as G++9, G++10. I replaced
with
in the head of file LoopClosing.h and this error was fixed. It works well with G++ 10.0.1, 9.3.0, 8.4.0, 7.5.0, 6.4.0 and 5.5.0.
My environmental information:
OS: Ubuntu 20.04 LTS
GNU GCC/G++: 10.0.1
cmake: 3.16.3
GNU make: 4.2.1
Pangolin: commit 86eb497
OpenCV: 3.2.0
Eigen: 3.2.10
Known problems:
It seems something wrong during Local BA. I can get following warnings if I build ORB_SLAM3 system in
DEBUGmode:More details : issue #24