You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I modify the pick and [place demo by adding a new planner (nvidia cumotion planner), I hit a segmentation fault when the task that uses the cumotion planner is executed. This is not any error in the cumotion planner which returns a plan successfully but my move it task mtc node is not being able to read the message and causing an Address not mapped error.
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
github-actionsbot
added
the
stale
Inactive issues and PRs are marked as stale and may be closed automatically.
label
Aug 8, 2024
Description
When I modify the pick and [place demo by adding a new planner (nvidia cumotion planner), I hit a segmentation fault when the task that uses the cumotion planner is executed. This is not any error in the cumotion planner which returns a plan successfully but my move it task mtc node is not being able to read the message and causing an Address not mapped error.
Your environment
Steps to reproduce
Add a new planner in the code:
Expected behaviour
The plan shou;ld be executed and shown in rviz
Actual behaviour
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.
The text was updated successfully, but these errors were encountered: