Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3AAE2174.B22F397C@ece.gatech.edu>
Date:	Tue, 13 Mar 2001 08:32:36 -0500
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer:	Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Gary_Rowe AT kindlesystems DOT com
CC:	cygwin AT cygwin DOT com
Subject:	Re: Strange behaviour of Signals under Cygwin
References:	<00256A0E DOT 0058B7DB DOT 00 AT SMTP-NOTES DOT Kindlesystems DOT com>

Gary_Rowe AT kindlesystems DOT com wrote:
> 
> Hi,
> 
> There appears to be a problem with signal handling in Cygwin, whereby
> it is possible under load for signals not to be delivered to the
> process they have been sent to when expected. However, they only
> appear to be deferred, and are delivered on receipt of a subsequent
> signal.
> 
> To test this, I used the following stand-alone program, and
> passed signals to it using the "kill(1)" command:

[snip]

> The output is similar, whether the program is compiled with
> "-DUSE_SIGACTION" or not.
> 
> Can anyone throw any light on this - is there something I'm missing, or is it
> something I'll have to live with?
> 
> And before you ask, NO, I haven't the experience (yet :-) to debug the Cygwin
> code and patch it!
> 

[snip]

There have been a number of recent patches to cygwin wrt signal handling
(and I seem to remember this very subject (deferred/delayed signal
delivery) being discusses on this list within the last two weeks...)

I would suggest trying a recent snapshot (e.g. last nights') but
apparently the snapshot build daemon is broken.  The most recent
snapshot is Mar 07 -- that one MAY have a few signal-related fixes; give
it a try.

--Chuck


>   615k 2001/01/31 c:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2001/1/31 20:38
>     Cygwin DLL version info:
>         dll major: 1001
>         dll minor: 8
>         dll epoch: 19
>         dll bad signal mask: 19005
>         dll old termios: 5
>         dll malloc env: 28
>         api major: 0
>         api minor: 34
>         shared data: 3
>         dll identifier: cygwin1
>         mount registry: 2
>         cygnus registry name: Cygnus Solutions
>         cygwin registry name: Cygwin
>         program options name: Program Options
>         cygwin mount registry name: mounts v2
>         cygdrive flags: cygdrive flags
>         cygdrive prefix: cygdrive prefix
>         cygdrive default prefix:
>         build date: Wed Jan 31 10:08:38 EST 2001
>         shared id: cygwin1S3

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -