I’m using zeromq 3.2.3 with the rbczmq ruby bindings gem, and have a simple case where ZeroMQ aborts due to an assert if I create a socket before calling fork().
If I create the socket after fork() then there is no abort. But if swap the two lines around, there is an assert. The symptoms look very similar to this bug in the perl bindings: https://github.com/lestrrat/ZeroMQ-Perl/issues/42 Except in my case, it’s the parent process that is having the assert, so there’s no possibility of confusion with the context because the parent process has only one context. Could it be that a child process exiting is triggering a SIGCHLD signal which is causing a “false positive” in the mailbox code? Has anyone else seen this before? Best, Matt _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
