No, I have not tried that yet. I don't believe from a precusory view that this is a bug in zeromq, since the errno in question is already specified in the manual page as a possible condition.
I suppose it is just a matter of having those semantics to deal with EINTR introduced in the various performance tests, under some form of a -DPROFILING_ENABLED macro. On 18/06/2012 20:02, Paul Colomiets wrote: > Hi, > > On Thu, Jun 14, 2012 at 1:29 PM, hp010170 <[email protected]> wrote: >> >> In case of [1], as you may know in REQ/REP examples, it is not just a >> matter of retrying, since that returns EFSM due to the strict >> alternating pattern; unless I have read the manual pages incorrectly. >> > > Have you tried to retry request? If you can't retry request after > EINTR, than its a critical bug in zeromq, and you should file a bug in > jira. > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
