[zeromq-dev] zmq::signaler_t::make_fdpair hangs application on crash

Felipe Farinon felipe.farinon at powersyslab.com
Mon Nov 11 16:16:24 CET 2013


Maybe we could change signaler_port to another value and define that 
port 5905 is protected by the Event and the new port (e.g. 5906) is 
protected by Mutex. This way we don't need to check if the Event is present.

Em 11/11/2013 11:16, Felipe Farinon escreveu:
> Ok.
>
> Seems reasonable to me and I think that a 4 seconds timeout is fine. 
> The only scenario where I could imagine that this would break is if 
> some heavy socket creation is going on and IFF the WaitForSingleObject 
> wakeup order for Events is not FIFO.
>
> Em 11/11/2013 11:02, KIU Shueng Chuan escreveu:
>>
>> Realistically, I think only bind, accept and connect have a chance of 
>> failing. The rest of the asserts just test for programming errors. 
>> Accept and connect are already handled. What's left is handling bind 
>> error.
>>
>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20131111/946f54be/attachment.html>


More information about the zeromq-dev mailing list