-
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
rmw_cyclonedds_cpp crashes when receiving a message on /rosout #126
Comments
Reproduced with the old versions (on dashing on macOS), confirmed fixed since Feb 4. This is ultimately a duplicate of #72. The 0.5.1 versions that should become available as apt packages in the near future will include the fix. Current master is also fine, just make sure you also get a matching Cyclone version (anything from Feb 5, and to get #127 to fix a recent mishap causing a build breakage for dashing & eloquent. |
Ok, thanks! |
@pjreed I think the binary (apt) version of cyclone is out now. Could you confirm and try it out? |
It looks like 0.5.1 is in the testing repository now: $ apt-cache policy ros-eloquent-rmw-cyclonedds-cpp
ros-eloquent-rmw-cyclonedds-cpp:
Installed: 0.5.1-1bionic.20200413.161250
Candidate: 0.5.1-1bionic.20200413.161250
Version table:
*** 0.5.1-1bionic.20200413.161250 500
500 http://packages.ros.org/ros2-testing/ubuntu bionic/main amd64 Packages I tested it and that seems to have fixed this problem. Thanks! |
Bug report
Required Info:
Steps to reproduce issue
rcl_interfaces:msg::Log
messages on/rosout
usingrmw_cyclonedds_cpp
/rosout
ros2 topic pub -1 /rosout rcl_interfaces/msg/Log
Here's an example program:
Expected behavior
The above client should not crash, but instead print
rosout:
followed by the log message.Actual behavior
The client crashes.
Additional information
The problem does not happen when subscribing to other topics. In the above example, it also creates a subscriber on
/rosout2
, and publishing a log message there will print as expected.Crashes do not occur when using
rmw_fastrtps_cpp
,rmw_opensplice_cpp
, orrmw_connext_cpp
.gdb catches this stack trace:
The text was updated successfully, but these errors were encountered: