diff options
| author | Christopher Faylor <me@cgf.cx> | 2012-05-07 19:28:40 +0400 |
|---|---|---|
| committer | Christopher Faylor <me@cgf.cx> | 2012-05-07 19:28:40 +0400 |
| commit | 51180c08ed6a11a2dab5dc8b591bab1e84054118 (patch) | |
| tree | 5271df9f0e5291b821cb1ff464e003eba96f3256 /winsup/cygwin/DevNotes | |
| parent | 06bd0ef2ab50252b81344d6810378b18f49c0e9c (diff) | |
Add additional observation to cgf-000003
Diffstat (limited to 'winsup/cygwin/DevNotes')
| -rw-r--r-- | winsup/cygwin/DevNotes | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/winsup/cygwin/DevNotes b/winsup/cygwin/DevNotes index 59cda286f..b9d031f1e 100644 --- a/winsup/cygwin/DevNotes +++ b/winsup/cygwin/DevNotes @@ -41,7 +41,9 @@ fix the problem. On further investigation, this seems to be caused by the fact that the shared memory region pid handles were still being passed to non-cygwin children, keeping the pid alive in a limbo-like fashion. This was easily fixed by having pinfo::init() consider a -memory region with PID_REAPED as not available. +memory region with PID_REAPED as not available. A more robust fix +should be considered for 1.7.15+ where these handles are not passed +to non-cygwin processes. This fixed the problem where a pid showed up in the list after a user does something like: "bash$ cmd /c start notepad" but, for some reason, |