From:	sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject:	RE: SIGKILL and blocking
16 Jun 1998 00:14:51 -0700 :
Message-ID:	<01BD9913.D7D104F0.cygnus.cygwin32.developers@sos>
To:	Christopher Faylor <cgf AT cygnus DOT com>, "'Tim Newsham'" <newsham AT lava DOT net>
Cc:	"cgf AT cygnus DOT com" <cgf AT cygnus DOT com>,
	"cygwin32-developers AT cygnus DOT com"
	<cygwin32-developers AT cygnus DOT com>

Tim Newsham wrote:
> ok, so, the other thread may have already consumed some bytes
> from the stream, or a packet from a connectionless socket.  Even
> worse, what does winsock do when you kill a thread that was making
> a call?  I would put my money on "break" based on other behavior I've
> seen from winsock.
> 

We have to recall about WSAXXX analogs of berkeley socket calls. All these calls are asynchronous.

-- 
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia

- Raw text -