delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/06/14/10:41:06

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: SIGKILL and block_sig_dispatch
14 Jun 1998 10:41:06 -0700 :
Message-ID: <01BD97DA.EFF075A0.cygnus.cygwin32.developers@sos>
To: "'Christopher Faylor'" <cgf AT cygnus DOT com>
Cc: "cygwin32-developers AT cygnus DOT com" <cygwin32-developers AT cygnus DOT com>

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().

> you could call do_exit in the context of the signal thread for the specific
> case of SIGKILL but what happens if there is a signal handler which calls
> exit() when something like a SIGTERM is received?  From your description,
> there will be a hang.

Why? 

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


- Raw text -


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