-
Notifications
You must be signed in to change notification settings - Fork 612
Fix seg fault with attached objects during motion execution #3466
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the segfault
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3466 +/- ##
==========================================
- Coverage 46.23% 45.84% -0.39%
==========================================
Files 718 718
Lines 62677 62662 -15
Branches 7583 7587 +4
==========================================
- Hits 28975 28720 -255
- Misses 33535 33775 +240
Partials 167 167 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Unfortunately this was still seg faulting here. Initializing current_attached_objects (which has raw pointers to the
|
(cherry picked from commit c81ac91) # Conflicts: # moveit_core/robot_state/src/robot_state.cpp # moveit_ros/planning/plan_execution/src/plan_execution.cpp
(cherry picked from commit c81ac91)
Description
#3327 introduced a bug where motion execution can segfault by attempting to indexing into arrays of zero length.
I assume this is because MTC sends execution requests where only the planing scene in modified, so trajectory lengths are zero. I also added some guards in robot_state to make sure we are not adding null objects to the
attached_bodies
list/map.