-
-
Notifications
You must be signed in to change notification settings - Fork 467
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
ToolManager: shortkey_to_tool_map_ not updated when removing tools #880
Labels
Comments
@hdeeken thanks, sorry I missed that in the review on the first go around. |
Bump, does anyone have time to look into this? |
hdeeken
added a commit
to hdeeken/rviz
that referenced
this issue
Aug 6, 2015
this should fix ros-visualization#880
hdeeken
added a commit
to hdeeken/rviz
that referenced
this issue
Aug 6, 2015
this should fix ros-visualization#880
@wjwwood the above patch should correctly manage the shortkey map now. i'm sorry for fixing this so late, i completely lost track of that! :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm part of a DRC team, and we have our own rviz fork. Since we have our own tools that use librviz, we don't use the tools that are initially inserted when you create a new visualization manager. So, we do
and then we add our own tools. I have just rebased our fork, and found that the following line caused issues:
https://github.com/ros-visualization/rviz/blame/indigo-devel/src/rviz/tool_manager.cpp#L140
It will insert a new uninitialized Tool* into shortkey_to_tool_map_ if it doesn't have that key in the map already, and causes the application to segfault a few lines after that when trying to set it as the current tool.
I'd suggest changing that line to the following:
Now, that by itself doesn't solve the issue that I'm having: shortkey_to_tool_map_ is never updated outside AddTool. After I remove all tools, shortkey_to_tool_map_ will retain all keys and invalid Tool*, causing it to crash.
The text was updated successfully, but these errors were encountered: