www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/06/22/08:51:50

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: SIGKILL and block_sig_dispatch
22 Jun 1998 08:51:50 -0700 :
Message-ID: <01BD9E13.AD70F3F0.cygnus.cygwin32.developers@sos>
Cc: "'cygwin32-developers AT cygnus DOT com'" <cygwin32-developers AT cygnus DOT com>

Sergey Okhapkin wrote:
> Christopher Faylor wrote:
> > >From your description of the problem, I'm not sure what that would solve.
> > Isn't the key thing to just ensure that WSACleanup is not called?  Sure,
> 
> Yes, I want to avoid a bug of WSACleanup().
> 

Looks like I've found a simple solution... It works for me fine. What do you think about?

exception.cc	(sig_handle): call close_all_files() instead of WSACleanup()
			to cancel all pending I/O.


--- exceptions.cc.orig  Sun Jun 07 03:01:48 1998
+++ exceptions.cc       Mon Jun 22 19:11:11 1998
@@ -655,8 +655,7 @@ stop:
        continue;

     exit_sig:
-      if (i_WSACleanup)
-       (*i_WSACleanup) ();
+      close_all_files ();
       sigproc_printf ("signal %d, about to call do_exit\n", sig);
       /* We encode the signal stuff in the high 8 bits.
         (sorta like the reverse of a standard wait)


-- 
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019