Revision history [back]

On the surface, this sounds like a bug in the roscpp publisher, but since this feature has existed in ROS for many years, that seems unlikely.

We're going to need quite a bit more information to debug this properly. You should edit your question to include: * The version of ROS and the OS that you're using * Which language the subscriber is written in * The versions of the roscpp and roscpp_core packages that you're using * The code for your C++ publisher which is giving you trouble

You may want to try writing the same publisher in python, to try to narrow down whether this is a difference between the python and C++ publishers, or if it's something wrong with the subscriber.

You may also want to try to reproduce this with the talker node from roscpp_tutorials and rospy_tutorials - those are "known good" nodes with well-defined behavior. If you can write a simple subscriber which reproduces this with the talker nodes, it should be easy to submit it as a bug report.

On the surface, this sounds like a bug in the roscpp publisher, but since this feature has existed in ROS for many years, that seems unlikely.

We're going to need quite a bit more information to debug this properly. You should edit your question to include: * include:

• The version of ROS and the OS that you're using * using
• Which language the subscriber is written in * in
• The versions of the roscpp and roscpp_core packages that you're using * using
• The code for your C++ publisher which is giving you trouble

You may want to try writing the same publisher in python, to try to narrow down whether this is a difference between the python and C++ publishers, or if it's something wrong with the subscriber.

You may also want to try to reproduce this with the talker node from roscpp_tutorials and rospy_tutorials - those are "known good" nodes with well-defined behavior. If you can write a simple subscriber which reproduces this with the talker nodes, it should be easy to submit it as a bug report.