From:	garbanzo AT hooked DOT net (Alex)
Subject:	RE: Cygwin32 Signals
24 Sep 1997 19:48:21 -0700 :
Message-ID:	<Pine.BSF.3.96.970924192730.508D-100000.cygnus.gnu-win32@zippy.dyn.ml.org>
References:	<01BCC901 DOT 176D4A80 AT gater DOT krystalbank DOT msk DOT ru>
Mime-Version:	1.0
To:	gnu-win32 AT cygnus DOT com

On Wed, 24 Sep 1997, Sergey Okhapkin wrote:

> Mikey wrote:
> > perhaps the following Psuedocode fragment will
> > give you some workable ideas.
> >
> 
> This may not help. Signal processing thread must suspend main thread 
> execution and switch it to signal handler routine. The only way to do it I 
> see is the current method (originally designed by Steve Chamberlain, the 
> inventor of gnu-win32 project): suspend the main thread execution, save 
> current inctruction pointer, set it to signal handler address and resume 
> main thread. Win95 may hang if context switching is while in a syscall. Why 
> did it work before? Because all the signal mechanism was almost missing in 
> cygwin.dll.

What about checking to see if you are making a call that could hang Win
and then either a.) waiting for the syscall to finish or b.) interrupt
that call?

- alex

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