X-Spam-Check-By:	sourceware.org
Date:	Fri, 27 Jan 2006 01:08:47 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included
Message-ID:	<20060127060847.GA14661@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<5 DOT 0 DOT 0 DOT 25 DOT 2 DOT 20060125101316 DOT 00bc8a30 AT pop3 DOT demon DOT co DOT uk>
Mime-Version:	1.0
In-Reply-To:	<5.0.0.25.2.20060125101316.00bc8a30@pop3.demon.co.uk>
User-Agent:	Mutt/1.5.11
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, Jan 25, 2006 at 10:19:14AM +0000, Lee Moore wrote:
>>>Mmm, IIRC signals can't be delivered unless you call cygwin functions.
>>
>>If that is actually true, it's a bug.  Cygwin should be able to
>>interrupt user code.  It doesn't try to interrupt...
>>
>>>int main(void) {
>>>       signal(SIGALRM,handler);
>>>       alarm(1);
>>>       Sleep();
>>>}
>>
>>...a Windows function like Sleep.  It should interrupt, e.g., a busy
>>loop in user code, however.
>
>are we agreed that this is a bug ?
>If so how can I get a fix, or a workaround to get me further ?

This may be fixed in the latest snapshot, which I'm generating right now.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -