On Wed, Sep 19, 2012 at 10:49 AM, Chuck Remes <[email protected]> wrote: > > On Sep 19, 2012, at 9:56 AM, Yi Ding wrote: > >> This is on linux with ZMQ 2.2.0 >> >> On Wed, Sep 19, 2012 at 9:49 AM, Yi Ding <[email protected]> wrote: >>> Hi everyone, >>> >>> I got a strange error today where one of my servers threw an assertion >>> when I killed a remote. >>> >>> Here's the error: >>> >>> Broken pipe (.../external/zmq/src/tcp_socket.cpp:229) >>> >>> Looking at it, it looks like it's just a recv call, but I'm not sure >>> why it would send back a EPIPE. > > Unfortunately, without a code snippet to reproduce the problem this kind of > report is useless. If you can figure out a way to reliably reproduce this > issue then we can try and fix it. > > cr >
It's the first time I've seen it myself. I'll try to see if there's a way to reproduce it, but was wondering more generally why we'd get a EPIPE on a TCP socket. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
