Thanks for your answer Kristian!
I tried a patch I got from Mortiz, compiled against the zeromq package in
the ArchLinux tree (3.2 I believe) and saw the same problems as well, but
I'll give this branch a spin later today and will create a sample program
to reproduce the error.
Cheers,
k
On
Hi Karsten,
It's a little hard to figure out why that socket all of a sudden just dies.
Perhaps you could make a smaller example where this bug is reproducable?
There is a branch where we're trying to update the bindings to work against
zmq version 3.2:
Hi List,
I'm having a strange problem with the zmq egg with the following program:
http://paste.call-cc.org/paste?id=1c0c94e23600b68e8100d6c5913f58368c01f02c
Basically, I have two sockets, one 'push for sending to a node.js
process (with the zmq module compiled against 2.1 series, too) and one
