-
Notifications
You must be signed in to change notification settings - Fork 91
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
Segmentation Fault in sdf::getBestSupportedModelVersion #152
Comments
Original comment by Dominic Jud (Bitbucket: djud). This is resolved. The issue was that we had an old definition of a sun where in the |
Original comment by Dominic Jud (Bitbucket: djud).
|
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). A similar issue has been posted on Gazebo: https://bitbucket.org/osrf/gazebo/issues/2238/gzserver-or-gazebo-76-crashes-on-startup We should try to handle this better so there are no crashes. |
Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
Let's' add a test case with a malformed model.config to confirm that it doesn't crash. |
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero). |
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero). pull request #327, thanks Dominic for the report and the workaround. My plan is to role a patch version of sdformat4 as soon as we get the PR merged. |
Original comment by Jose Luis Rivero (Bitbucket: Jose Luis Rivero, GitHub: j-rivero).
version 4.3.1 is in the repo. Please reopen if the issue still persists for you. |
Original report (archived issue) by Dominic Jud (Bitbucket: djud).
Since the last update of sdformat4, there is a segmentation fault occurring that was not there before the update. I'm using gazebo7 and Ubuntu 14.04. The backtrace goes to sdf::getBestSupportedModelVersion.
Log with the backtrace from GDB when running gazebo:
@scpeters As the author of the related PR: Is this a general bug or might it be a problem specific to me?
The text was updated successfully, but these errors were encountered: