RTT::FileDescriptorActivity and hasError()

Submitted by matthiasgoldhoo... on Fri, 2014-09-05 08:14

i just discovered that the RTT::FileDescriptorActivity::hasError()
function returns true if a file descriptor read was interrupted by a
System interrupt.

(errno -4), this is afaik not a error in general, the hasError()
function should only return critical errors, from my point of view if a
read is too often interrupted the timeout should catch. I would like
therefore to modify the function that errnor -4 is ignored.

Thougts?

Best,
Matthias

‹ KDL in ROS - error in kdl/jntspaceinertiamatrix.hpp? [Rock-dev] TaskInspector influences TaskExecutoin ›
»

RTT::FileDescriptorActivity and hasError()

Submitted by snrkiwi on Wed, 2014-09-17 13:12.

On Sep 05, 2014, at 04:14, Matthias Goldhoorn <matthias [dot] goldhoorn [..] ...> wrote:

> i just discovered that the RTT::FileDescriptorActivity::hasError()
> function returns true if a file descriptor read was interrupted by a
> System interrupt.
>
> (errno -4), this is afaik not a error in general, the hasError()
> function should only return critical errors, from my point of view if a
> read is too often interrupted the timeout should catch. I would like
> therefore to modify the function that errnor -4 is ignored.
>
> Thougts?

Where errno-4 == EINTR, I think that this should be configurable. Not all applications will want to ignore this, while some will want to ignore it. I don’t think we can make a global policy decision here.

YMMV
S

»