aboutsummaryrefslogtreecommitdiff
path: root/tests/server
diff options
context:
space:
mode:
authorMarc Hoersken <info@marc-hoersken.de>2013-04-06 10:03:43 +0200
committerMarc Hoersken <info@marc-hoersken.de>2013-04-06 10:03:43 +0200
commite3787e862f6589ee6f5db36eb24a81f27f876cda (patch)
tree17539c3325aa62ff15db7cbeab09f6ecdddf14bd /tests/server
parent6eb56e72de1356d6f5f52a80be487a68ec463cf9 (diff)
util.c: Follow up cleanup on eeefcdf
Diffstat (limited to 'tests/server')
-rw-r--r--tests/server/util.c14
1 files changed, 7 insertions, 7 deletions
diff --git a/tests/server/util.c b/tests/server/util.c
index bd6542826..22e42bb65 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
* \
- * <proc>.exe <-- waiting Windows process
+ * <proc>.exe <-- waiting Windows process, but not visible to Msys
* \
- * <proc>.exe <-- running Windows process
+ * <proc>.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);
}