From c282e64f1f1f566265d5d695920f6527ea6e7ece Mon Sep 17 00:00:00 2001
From: Brad King <brad.king@kitware.com>
Date: Mon, 19 May 2014 10:53:51 -0400
Subject: [PATCH] Process: Workaround child kill trouble on Cygwin

When we kill a child we send SIGSTOP first so that we can traverse its
child processes recursively.  On unwinding the recursion we then send
SIGKILL.  Current Cygwin has trouble when both signals are sent in quick
succession by the parent process.  Add a usleep(1) after sending the
first signal to give up our time slice and give Cygwin a chance to
process the first signal before sending the second.

Change-Id: I75ab55cf969a0ea6104a9798c761c0ba1fcd1dbc
---
 ProcessUNIX.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/ProcessUNIX.c b/ProcessUNIX.c
index faeb967..241e295 100644
--- a/ProcessUNIX.c
+++ b/ProcessUNIX.c
@@ -2413,6 +2413,12 @@ static void kwsysProcessKill(pid_t process_id)
   /* Suspend the process to be sure it will not create more children.  */
   kill(process_id, SIGSTOP);
 
+#if defined(__CYGWIN__)
+  /* Some Cygwin versions seem to need help here.  Give up our time slice
+     so that the child can process SIGSTOP before we send SIGKILL.  */
+  usleep(1);
+#endif
+
   /* Kill all children if we can find them.  */
 #if defined(__linux__) || defined(__CYGWIN__)
   /* First try using the /proc filesystem.  */
-- 
GitLab