summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCorinna Vinschen <corinna@vinschen.de>2015-12-15 17:14:08 +0100
committerCorinna Vinschen <corinna@vinschen.de>2016-06-24 22:49:48 +0200
commitb87224fba54587141253fe960f1134dcda94ddc4 (patch)
tree1e820c30aa988ca8b512142f979b21b66cc4a8fb
parentecea7536893da487c6d38d29223150d3025d6068 (diff)
downloadcygnal-b87224fba54587141253fe960f1134dcda94ddc4.tar.gz
cygnal-b87224fba54587141253fe960f1134dcda94ddc4.tar.bz2
cygnal-b87224fba54587141253fe960f1134dcda94ddc4.zip
child_info::child_info: Fix a comment
-rw-r--r--winsup/cygwin/sigproc.cc9
1 files changed, 2 insertions, 7 deletions
diff --git a/winsup/cygwin/sigproc.cc b/winsup/cygwin/sigproc.cc
index 4ebcb0a8f..60c931de3 100644
--- a/winsup/cygwin/sigproc.cc
+++ b/winsup/cygwin/sigproc.cc
@@ -776,13 +776,8 @@ child_info::child_info (unsigned in_cb, child_info_types chtype,
This seems to be a bug in Vista's WOW64, which apparently copies the
lpReserved2 datastructure not using the cbReserved2 size information,
but using the information given in the first DWORD within lpReserved2
- instead. 32 bit Windows and former WOW64 don't care if msv_count is 0
- or a sensible non-0 count value. However, it's not clear if a non-0
- count doesn't result in trying to evaluate the content, so we do this
- really only for Vista 64 for now.
-
- Note: It turns out that a non-zero value *does* harm operation on
- XP 64 and 2K3 64 (Crash in CreateProcess call).
+ instead. However, it's not clear if a non-0 count doesn't result in
+ trying to evaluate the content, so we do this really only for Vista 64.
The value is sizeof (child_info_*) / 5 which results in a count which
covers the full datastructure, plus not more than 4 extra bytes. This