Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix segmentation fault on exit #111

Closed
at-wat opened this issue Jul 11, 2019 · 1 comment · Fixed by #120
Closed

Fix segmentation fault on exit #111

at-wat opened this issue Jul 11, 2019 · 1 comment · Fixed by #120

Comments

@at-wat
Copy link
Member

at-wat commented Jul 11, 2019

No description provided.

@at-wat
Copy link
Member Author

at-wat commented Nov 19, 2019

This occurs mainly as ypspur_ros child process.
ypspur_ros tries to kill ypspur-coordinator by SIGINT immediately after communication error caused by device connection error.
In this case, termination sequence runs twice in ypspur-coordinator and causes segmentation fault.

@at-wat at-wat mentioned this issue Nov 19, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Trap SIGINT only in odometry receive loop openspur/yp-spur
1 participant
@at-wat