This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Cygwin32 Signals
- To: gnu-win32 at cygnus dot com
- Subject: Re: Cygwin32 Signals
- From: cgf at bbc dot com (Chris Faylor)
- Date: Fri, 26 Sep 1997 15:59:48 GMT
- Organization: Boston Business Computing, Ltd.
- References: <01BCCA67.FB0348F0@gater.krystalbank.msk.ru>
- Reply-To: cgf at bbc dot com
In article <01BCCA67.FB0348F0@gater.krystalbank.msk.ru>,
Sergey Okhapkin <sos@prospect.com.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@bbc.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@cygnus.com" with one line of text: "help".