Segmentation fault caused by conflict between ion-kit and ROS Client Library in spdlog usage
- Dominant language
- C++
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
A segmentation occurs at the end of a program when using ion-kit with the rcl in a C++ environment.
Both ion-kit and rcl utilize the `spdlog::logger` class and this caused ion-kit tries to access the logger instance after rcl cleans it up.
Tentatively we disabled the use of `spdlog::logger` by `set_level`, and we can test the change of the `spdlog:logger` in ion-kit to a local instance to avoid this conflict. Further testing is required to confirm if this solution effectively resolves this issue.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the segmentation fault in a C++ program that uses ion-kit with the ROS Client Library, as described in the issue. Compare the tentative set_level change with using a local spdlog::logger instance in ion-kit; done means the program exits without a segmentation fault and the behavior is confirmed by further testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100