Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Wed, 14 Jun 2000 09:51:30 -0400
From: tosh <tosh AT cyberspace DOT org>
Message-Id: <200006141351.JAA22844@grex.cyberspace.org>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: signal implementation bugs

Hi, there,

i have been trying to use the latest version of Cygwin to 
port a simple program that uses TCP sockets. the program 
uses blocking calls, such as recv(), connect(), or accept(), 
and uses alarm() to set timeouts on them. much to my 
disappointment, i found that signal delivery does not 
interrupt these calls under cygwin. not only that, but 
doing siglongjump() from the signal handler to the main 
program (in order to abort the timed out blocked call), 
also doesn't work. is there any way to fix this? other
than using non-blocking i/o and select() which i assume
would work.

tosh

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com