-
Notifications
You must be signed in to change notification settings - Fork 90
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
failing ros1_bridge tests #72
Labels
bug
Something isn't working
Comments
The type support is indeed cached in the topic. This is something that needs to be changed in Cyclone for mixed-language use and not very difficult (and I'm all in favour of it). |
Resolved by #96. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://ci.ros2.org/view/packaging/job/packaging_linux/1675/testReport/ which is trying to run a ROS 1 talker, the ros1_bridge
dynamic_bridge
, and ROS 2 listener.The problem for the failure seems pretty similar to ros2/rmw_fastrtps#265. The logging messages are published as a C message containing a string. The actual message exchanged between the talker and listener is a C++ message (based on the same
.msg
). I assume the first advertised topic will "lock in" the C message type and then falsely try to use the same typesupport to read the C++ message which fails withrealloc(): invalid pointer
.The text was updated successfully, but these errors were encountered: