Christopher Faylor wrote:
I don't know if this is what you are seeing but If you are blocked in a Windows function like WaitMessage or WaitForSingleObject, the signal will not be delivered until some random time after you leave the function.
Alright, that's what it is then.
One way around this is to start a thread and wait for signals in that thread.
I've added a thread doing 'for (;;) pause();', but unfortunately that doesn't seem to do the trick. Do I need to go into Cygwin internals and wait directly on the Win32 event(s) used for signals?
Andy -- 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/
