From: newsham AT aloha DOT net (Tim Newsham)
Subject: signals and blocking calls
26 Jun 1997 15:16:19 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199706262110.LAA15568.cygnus.gnu-win32@haleakala.aloha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Original-To: gnu-win32 AT cygnus DOT com
X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*]
Original-Sender: owner-gnu-win32 AT cygnus DOT com


Hi,

    I've noticed that there are some times when I cannot
get a signal delivered to a process.  For examle when I
am reading from a socket and the read blocks, signals seem to 
not get delivered (until the read unblocks).  If the
read blocks permanently, the program is unkillable
and unsignallable.  Is there anything I can do (short of
using a seperate thread or non-blocking I/O) to get
reliable signalling ? 

                                Tim N.

(I can provide example code if necessary).
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".