ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

1

why "simple message" classes are not thread safe?

asked 2017-12-11 07:09:08 -0500

ManMan88
44 ●7 ●9 ●13

updated 2017-12-11 07:12:14 -0500

Why does all of the industrial simple message package classes has a warning: THIS CLASS IS NOT THREAD-SAFE? What makes them not thread safe?

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

3

answered 2017-12-11 08:53:04 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2017-12-11 08:53:46 -0500

What makes them not thread safe?

The message classes are (de)serialising C-structs from/to a byte buffer.

Buffer accesses are not thread safe, as they don't lock any of the resources that they use.

In addition to that reading and writing bytes from/to the network socket file descriptor is not guarded either.

edit flag offensive delete link

Question Tools

3 followers

Stats

Asked: 2017-12-11 07:09:08 -0500

Seen: 133 times

Last updated: Dec 11 '17

Related questions

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2