-
Notifications
You must be signed in to change notification settings - Fork 609
Move_group exits with segmentation fault when receiving a SIGINT #3268
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
Comments
This is problematic specially for all test checking exit codes, because move_group makes them fail. |
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. |
Hello, I can deal with this issue. AFAIK, If I am not wrong, I sorted out this in somewhere by resetting some interface/node instances here (please don't take into account the comments which is badly written). It seems to me that the issue can be related to the order of destroying instances. will try to take a look this weekend. |
Hello, @JorgePH , firstly thank you for feedbacking us about it and sorry for delayed response. I think I have a patch for it. Will clean up it and make it ready to merge tomorrow. When everything is ready, I will want you to give a feedback to me. Not now. Just for updating this thread. |
Description
I am receiving a segmentation fault when trying to close move_group node (with Ctrl+C or sending SIGINT).
ROS Distro
Jazzy
OS and version
Ubuntu 24.04.1 LTS
Source or binary build?
Binary
If binary, which release version?
2.12.1-1noble.20241228.033527
If source, which branch?
No response
Which RMW are you using?
CycloneDDS
Steps to Reproduce
Launch ur sim moveit demo (or any other package containing move_group):
Close it with Ctrl+C
Expected behavior
All process should close with exit code -2.
Actual behavior
Move_group node returns a exit code -11, and prints a Segmentation fault error:
The complete error is:
Backtrace or Console output
https://gist.github.com/JorgePH/03bff938f42c78cd6256a0b379619db1
The text was updated successfully, but these errors were encountered: