it ain’t pretty, but i have always been able to resolve these by adding simple debugging printf lines at socket open and close.
On Apr 1, 2014, at 6:24 AM, Pieter Hintjens <[email protected]> wrote: > There's no way to see what's hanging. This is still a poorly built > part of libzmq. > > The best way to debug this is to make a test case and strip that down > until it works. > > On Tue, Apr 1, 2014 at 2:59 PM, Michi Henning <[email protected]> wrote: >> Hi, >> >> I'm looking for some advice on how to debug a hang in zmq_ctx_term(). >> >> Basically, I have a number of sockets in use in my program. They all set the >> linger timeout to zero (or a small wait time, on the order of 300 ms). >> >> When I finally shutdown (via the zmqpp::context destructor), I end up >> hanging in zmq_ctx_term(). This doesn't happen deterministically--I get the >> hang once in about twenty tries or so. When the hang occurs, all my threads >> have terminated, and the only threads remaining are the main thread, plus >> two internal threads created by zmq. >> >> I know that terminating requires all sockets to be closed, and I believe >> that I'm actually closing them properly. >> >> My question is whether there is any way to figure out *why* zmq_ctx_term() >> waits indefinitely. Is there a way to see what exactly zmq_ctx_term() is >> waiting for? >> >> Thanks, >> >> Michi. >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev ----------------------- Andrew Hume 949-707-1964 (VO and best) 732-420-0907 (NJ) [email protected]
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
