Skip to content
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

topic_tools: demux crashes when using __none #1366

Closed
lfdebrux opened this issue Apr 16, 2018 · 4 comments
Closed

topic_tools: demux crashes when using __none #1366

lfdebrux opened this issue Apr 16, 2018 · 4 comments

Comments

@lfdebrux
Copy link
Contributor

lfdebrux commented Apr 16, 2018

The demux node in topic_tools crashes when it receives a message and the selected topic is the magic "__none" topic

Steps to reproduce

rosrun topic_tools demux in out_1 out_2
rosservice call /demux/select "__none"
rostopic pub -1 /in std_msgs/Empty

demux then crashes with a segmentation fault

This was tested in kinetic on Ubuntu 16.04.

I believe this is due to a null pointer dereference in

g_selected->pub->publish(msg);

@lfdebrux lfdebrux changed the title Demux crashes when using __none topic_tools: demux crashes when using __none Apr 16, 2018
lfdebrux pushed a commit to RALSpaceASG/ros_comm that referenced this issue Apr 16, 2018
@peci1
Copy link
Contributor

peci1 commented Feb 18, 2020

Argh... bumped into this now on melodic... When will there finally be a new release of ros_comm???

@peci1
Copy link
Contributor

peci1 commented Feb 18, 2020

For others who suffer by this bug: as a workaround, you can always add a "blackhole" topic which nobody subscribes, and redirect the output to it instead of __none.

@dirk-thomas
Copy link
Member

Argh... bumped into this now on melodic... When will there finally be a new release of ros_comm???

This issue was closed when the referenced commit was merged: 2b3f43d on Apr 24, 2018. And that commit has been released for a very long time into Melodic (around May 2018). So if you still experience issues you might want to double check if there is an open ticket describing it or create a new issue.

@peci1
Copy link
Contributor

peci1 commented Feb 19, 2020

You're right, in the end it looks like a different issue, but with very similar symptoms. See #1889 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants