delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/06/15/05:51:41

From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: RE: SIGKILL and block_sig_dispatch
15 Jun 1998 05:51:41 -0700 :
Message-ID: <199806151212.IAA11735.cygnus.cygwin32.developers@kramden.cygnus.com>
To: cgf AT cygnus DOT com, sos AT prospect DOT com DOT ru
Cc: cygwin32-developers AT cygnus DOT com

>From: Sergey Okhapkin <sos AT prospect DOT com DOT ru>
>Date: Mon, 15 Jun 1998 08:07:37 +0400
>
>Chris, I never told about SIGKILL! I'm talking about any _unhandled_ 
>signal, whose default disposition is to terminate a process. If do_exit() 
>will be called in a context of signal thread, we'll not need WSACleanup() - 
>ExitProcess() call will make all neccessary cleanup for us.

Ok.  Forget about SIGKILL.  My point still stands.  If what you are
describing is correct, it will be possible to hang a cygwin application
of a signal handler calls exit().

- Raw text -


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