diff options
author | Christopher Faylor <me@cgf.cx> | 2004-03-09 01:29:39 +0000 |
---|---|---|
committer | Christopher Faylor <me@cgf.cx> | 2004-03-09 01:29:39 +0000 |
commit | d8672e934309be04b2aec7fc22a8467a63b77f68 (patch) | |
tree | 84d5618b5f62b524471c19dd6f844ca08d9bbfe4 | |
parent | 5fb0fe79eb76f59ac5d88e15c38b6e7bc63f9c91 (diff) | |
download | cygnal-d8672e934309be04b2aec7fc22a8467a63b77f68.tar.gz cygnal-d8672e934309be04b2aec7fc22a8467a63b77f68.tar.bz2 cygnal-d8672e934309be04b2aec7fc22a8467a63b77f68.zip |
.
-rw-r--r-- | winsup/cygwin/how-signals-work.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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. |