This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 27 Jan 2006 01:08:47 -0500
- Subject: Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included
- References: <5.0.0.25.2.20060125101316.00bc8a30@pop3.demon.co.uk>
- Reply-to: 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/