-
Notifications
You must be signed in to change notification settings - Fork 486
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
Laser Visual segmentation fault #950
Comments
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Thanks, I'll make a pull request. |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters). |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
|
Original comment by amirhosein_shantia (Bitbucket: amirhosein_shantia). Is this fix also applied to the ubuntu apt repo? |
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero). The patch was added to gazebo 1.9 branch a bit after release 1.9.2 and it is present in our latest released version 1.9.3. The osrf repository hosts the 1.9.3 version while the ROS repo still have the 1.9.2, so you would need to enable the osrf repository or just download and install the package manually. |
Original comment by amirhosein_shantia (Bitbucket: amirhosein_shantia). Thanks, I got the 1.9.3 binary package from your link. It works great. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original report (archived issue) by François-Michel De Rainville (Bitbucket: fmder).
In the LaserVisual constructor of branch 1.9, the OnScan callback is registered before the first point is added to rayFan. When the computers slows down (in big simulations) this leads to a segmentation fault in the OnScan callback (the rayFan->SetPoint(0, ...) line).
In version 2.0, this has been fixed in the rewrite of the component.
Bringing the subscription of the callback on the last line solved the problem for me.
The text was updated successfully, but these errors were encountered: