Message-ID: <496A24DE.1080101@gmail.com>
Date: Sun, 11 Jan 2009 16:57:02 +0000
From: Andy Koppe <andy.koppe@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Signal handling in Win32 GUI programs
References: <496A1DBC.7070004@gmail.com> <20090111163729.GB9992@ednor.casa.cgf.cx>
In-Reply-To: <20090111163729.GB9992@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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/