From: cgf AT bbc DOT com (Chris Faylor)
Subject: Re: Cygwin32 Signals
26 Sep 1997 09:18:30 -0700
Message-ID: <EH4Hro.405.cygnus.gnu-win32@bbc.com>
References: <01BCCA67 DOT FB0348F0 AT gater DOT krystalbank DOT msk DOT ru>
Reply-To: cgf AT bbc DOT com
To: gnu-win32 AT cygnus DOT com

In article <01BCCA67 DOT FB0348F0 AT gater DOT krystalbank DOT msk DOT ru>,
Sergey Okhapkin  <sos AT prospect DOT com DOT ru> wrote:
>Trevor Yann wrote:
>> The current signal handling code processes signals in the user's thread.
>> If signals were processed in a separate thread I don't think that
>> Windows95 would have a problem:
>>
>> 1.	suspend user thread (don't care whether or not it is doing
>> 	system stuff)
>> 2.	invoke signal handling
>> 3.	resume user thread
>>
>> Unfortunately there is software that assumes that signals are processed
>> in the user's context - functions like longjmp will only work if signals
>> are processed in the user's thread.
>
>It's the cause of executing signal handler in main thread. Hopefully Chris 
>Faylor solved most of Win95-specific problems. His patch is now in 
>testing/fixing stage.

Actually, right now, it's in the testing/scratching-head-perplexedly phase.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".