Sustrik and mato, I just tested this idea of having the blocking recv and poll not trap and silence EINTR. It work exactly like we want, at least on OS X. I just put in a print statement that prints if EINTR is returned, and if my program is sitting in blocking recv and I send SIGINT, the print statement is triggered at the right time. Thus, if zeromq starts to simply return EINTR for any blocking call (recv, poll, etc) all language bindings will be able to properly handle signals in blocking calls. BUT, one big question...
This issue is the biggest one that we face with both 2.0.7 and 2.0.8. Would it be possible to back port this fix to both of these branches as well? But that would mean releasing 2.0.7.1 and 2.0.8.1. I guess an alternative would be to release a 2.0.9 that branches off 2.0.8 and has this fix. It would be a huge pain for us if this didn't show up until 2.1. Do you think this is possible? Cheers and many thanks! Brian _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
