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: Signal handling in Win32 GUI programs


On Sun, Jan 11, 2009 at 04:57:02PM +0000, Andy Koppe wrote:
> 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?

sigwait() will probably work better than pause.

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]