[zeromq-dev] weird bug

AJ Lewis aj.lewis at quantum.com
Mon Mar 5 17:51:23 CET 2012


It looks like this commit made similar changes to other calls:

commit 91ea20464439b5359a5d803181141fc756fa817c
Author: Martin Sustrik <sustrik at 250bpm.com>
Date:   Wed Sep 8 08:39:27 2010 +0200

    EINTR returned from the blocking functions


This came in just before 2.1.10.

Regards,
AJ

On Mon, Mar 05, 2012 at 02:09:37AM +0100, Pieter Hintjens wrote:
> On Sun, Mar 4, 2012 at 11:30 PM, Andrew Hume <andrew at research.att.com> wrote:
> 
> > really? it wasn't mentioned in the "what's changed logs",
> > and represents a semantic change.
> > i hope someone like martin or pieter can speak to this..
> 
> commit 3cb929e46affd5ebf8c456acba594bae5c106cc8
> Author: Martin Sustrik <sustrik at 250bpm.com>
> Date:   Thu Jul 21 23:35:26 2011 +0200
> 
>     mailbox::recv correctly passes EINTR to the caller
>     This bug caused signal during blocking call to assert.
>     Signed-off-by: Martin Sustrik <sustrik at 250bpm.com>
> 
> It looks like this change didn't have an issue, and got into 2.1.8
> without proper documents.
> 
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-- 
AJ Lewis
Software Engineer
Quantum Corporation

Work:    651 688-4346

----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.



More information about the zeromq-dev mailing list