From:	sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject:	RE: Cygwin32 Signals
25 Sep 1997 23:54:06 -0700 :
Message-ID:	<01BCCA67.FB0348F0.cygnus.gnu-win32@gater.krystalbank.msk.ru>
To:	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>,
	"'Trevor Yann'"
	<TYann AT vet DOT com DOT au>

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.

--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job.


-
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".

- Raw text -