OK, I've fixed the problem: https://github.com/zeromq/czmq/pull/525
On Fri, Jun 13, 2014 at 8:14 PM, Michel Pelletier
wrote:
>
>
>
> On Fri, Jun 13, 2014 at 11:08 AM, Pieter Hintjens wrote:
>>
>> On Fri, Jun 13, 2014 at 7:55 PM, Michel Pelletier
>> wrote:
>>
>> > Some gdb adventures shows I was
On Fri, Jun 13, 2014 at 11:08 AM, Pieter Hintjens wrote:
> On Fri, Jun 13, 2014 at 7:55 PM, Michel Pelletier
> wrote:
>
> > Some gdb adventures shows I was calling zsock_new with filename and
> line_nbr
> > args defaulting to NULL and 0 out of sheer laziness.
>
> That should actually work... it'
On Fri, Jun 13, 2014 at 7:55 PM, Michel Pelletier
wrote:
> Some gdb adventures shows I was calling zsock_new with filename and line_nbr
> args defaulting to NULL and 0 out of sheer laziness.
That should actually work... it's usually what you'd do in release
mode with all socket tracking switched
Some gdb adventures shows I was calling zsock_new with filename and
line_nbr args defaulting to NULL and 0 out of sheer laziness. When I set
them (to anything) the program exits normally. I can easily get the file
and line nbr of the Python caller so I'll just shove those in there.
Should have t
It sounds like there's another socket being created somewhere, outside
of CZMQ's control, and this is causing the termination to block.
Or, something weird with threads. Can you try adding tracing to each
socket creation and destruction, in zsys (zmq_socket/zmq_destroy)?
On Fri, Jun 13, 2014 at 4
I'm working on adding zsock and zactor support to pyczmq, and I have most
of the work done, but my test for zsock is hanging. The test runs and
works, zsock_destroy is called correctly (not that it would matter the
default linger is 0) but the process never exits. gdb says it hanging on
poll in z
