Fix joint controller with empty joint velocity data #937
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Ian Chen ichen@osrfoundation.org
🦟 Bug fix
Summary
Joint controller system assumes that joint velocity data is always available and tries to access the data by indexing into an
std::vector
object. However, if the physics system is not loaded, the vector will be empty and the system will throw an'std::out_of_range'
error. This PR checks for empty vector before doing any indexing.One example of this happening is when trying to run the collada exporter of a model that has a joint controller but in a world without the physics system.
To reproduce:
Here's the world file
tmp_world.sdf
and run this cmd:
Without the changes in this PR, you should get a crash with backtrace pointing to the joint controller system
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge