From d8672e934309be04b2aec7fc22a8467a63b77f68 Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Tue, 9 Mar 2004 01:29:39 +0000 Subject: [PATCH] . --- winsup/cygwin/how-signals-work.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/winsup/cygwin/how-signals-work.txt b/winsup/cygwin/how-signals-work.txt index 9a2b47853..cc0b26ff8 100644 --- a/winsup/cygwin/how-signals-work.txt +++ b/winsup/cygwin/how-signals-work.txt @@ -6,7 +6,7 @@ How do signals work? On process startup, cygwin starts a secondary thread which deals with signals. This thread contains a loop which blocks waiting for -information to show up on a pipe whose handle (sendsig) is currently +information to arrive on a pipe whose handle (sendsig) is currently stored in _pinfo (this may change). Communication on the sendsig pipe is via the 'sigpacket' structure.