From e3787e862f6589ee6f5db36eb24a81f27f876cda Mon Sep 17 00:00:00 2001 From: Marc Hoersken Date: Sat, 6 Apr 2013 10:03:43 +0200 Subject: [PATCH] util.c: Follow up cleanup on eeefcdf --- tests/server/util.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/tests/server/util.c b/tests/server/util.c index bd65428..22e42bb 100644 --- a/tests/server/util.c +++ b/tests/server/util.c @@ -257,14 +257,14 @@ int wait_ms(int timeout_ms) * * These functions make it possible to get the Msys PID instead of the * Windows PID assigned to the current process. This is done by walking up - * to the Msys sh.exe process that launched the shadow Windows processes. + * to the Msys sh.exe process that launched the actual Windows processes. * - * Usually an Msys process would result in following process tree: - * sh.exe <-- waiting Windows process, but running Msys process + * Usually an Msys process would result in the following process tree: + * sh.exe <-- waiting Windows process, but visible Msys process * \ - * .exe <-- waiting Windows process + * .exe <-- waiting Windows process, but not visible to Msys * \ - * .exe <-- running Windows process + * .exe <-- running Windows process, but not visible to Msys * * Attention: This may not be true for all Msys processes. */ @@ -282,7 +282,7 @@ static pid_t getpid_msys(void) if(snapshot != INVALID_HANDLE_VALUE) { walk = TRUE; - while(walk) { + do { if(Process32First(snapshot, &entry)) { do { if(pid == entry.th32ProcessID) { @@ -295,7 +295,7 @@ static pid_t getpid_msys(void) } } while (Process32Next(snapshot, &entry)); } - } + } while(walk); CloseHandle(snapshot); } -- 2.7.4