[zeromq-dev] exception from recv()

Doherty, Kevin Kevin.Doherty at mlp.com
Thu Sep 27 19:24:24 CEST 2012


strace it

could be all manner of reasonable signals that may
be caught by other threads most of the time.
Retrying the operation seems to be the thing to do.
tx

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Ian Barber
Sent: Thursday, September 27, 2012 1:21 PM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] exception from recv()

On Thu, Sep 27, 2012 at 4:11 PM, Tom Wilberding <tom at wilberding.com> wrote:

> Thanks Ian but my reading of zmq.hpp and the release notes is that it 
> is throwing if it isn't EGAIN (not EINTR). I looked at the java 
> bindings they have similar logic.
>

Ah yes, you're right, sorry, careless reading.

> I should also point out that I have no idea what is the root cause of 
> the interrupted system call. It can run for hours without it 
> occurring, but I've found a few ways to induce it to happen, so if 
> anyone has some debugging tips, I'd appreciate the help. I'm not 
> sending SIGINT/^C to my app, there is something else going on. Is 
> receiving EINTR during a
> zmq_recv() for anything other than a SIGINT/^C something that others 
> are familiar with?

Do vaguely recall Andrew Hume having an issue of a similar nature - might be worth searching the list archives.

Ian
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
######################################################################
The information contained in this communication is confidential and
may contain information that is privileged or exempt from disclosure
under applicable law. If you are not a named addressee, please notify
the sender immediately and delete this email from your system.
If you have received this communication, and are not a named
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
######################################################################



More information about the zeromq-dev mailing list