From:	cgf AT cygnus DOT com (Christopher Faylor)
Subject:	Re: connect vs. signals
8 May 1998 05:47:23 -0700 :
Message-ID:	<199805081236.IAA26510.cygnus.cygwin32.developers@kramden.cygnus.com>
To:	cygwin32-developers AT cygnus DOT com, newsham AT lava DOT net

>putting
>
>      block_sig_dispatch();
>and
>      allow_sig_dispatch();
>
>around the i_connect call in cygwin32_connect() fixes the signal/connect
>race condition demonstrated in the test program I posted earlier.  This
>should probably be added to the main sources.

If I remember correctly, it wasn't a race condition, was it?  I thought
things just behaved badly in a user supplied signal handler routine
if connect was interrupted.  Putting these around the i_connect call
makes the connect uninterruptable.  Is that correct?

cgf

- Raw text -