-
Notifications
You must be signed in to change notification settings - Fork 310
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
std::bad_alloc crash in robot_description_callback #1986
Comments
Hello @tonynajjar, Thank you for reporting it. Can you please share the ros2_control tag information inside your URDF?. I'm not sure if this is coming from the recent commit, as we have tests internally that are working. I would suggest to remove the installed Thank you |
I will check if it works with the binaries without having anything in source |
The above one should work AFAIK. Can you check source only without any binaries of hardware_interface?
Looking at your log, I see that the gz_ros2_control is being used from the binaries. Remember that it is linking againsyt installed binary instead of your local one. Try also compiling this locally |
When building
I guess I would also need to build gz_msgs_vendor/gz_msgs from source which doesn't seem so simple (or at least I don't know how because it's vendored). Do you know a way? This is the installed version:
|
@tonynajjar are you using the jazzy branch?. If so, try with the last tag and see if it works |
sorry forgot to mention, yes I'm using the jazzy branch. I don't want to take too much of your time on what I believe is like you say, an issue with my setup e.g binary mismatch. I will try a bit more and if I can't get it to work I'll just pin my fork to before that problematic commit. |
Sure. No worries. Thank you. Keep us posted :) |
Describe the bug
@saikishor I localized that after this commit I get the following crash.
I don't really see the relation though, do you?
Screenshots
Environment (please complete the following information):
Additional context
Add any other context about the problem here, especially include any modifications to ros2_control that relate to this issue.
The text was updated successfully, but these errors were encountered: