This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]