X-Spam-Check-By:	sourceware.org
Message-Id:	<5.0.0.25.2.20060125101316.00bc8a30@pop3.demon.co.uk>
X-Sender:	moore+imperas2-adsl AT pop3 DOT demon DOT co DOT uk
Date:	Wed, 25 Jan 2006 10:19:14 +0000
To:	cygwin AT cygwin DOT com
From:	Lee Moore <moore AT imperas DOT com>
Subject:	Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included
Mime-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Hi Chris, Samuel,

> >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.
>
>cgf

are we agreed that this is a bug ?
If so how can I get a fix, or a workaround to get me further ?

Thx
Lee



--
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 -