Pierre A. Humblet
Fri Jan 7 03:52:00 GMT 2005
* pinfo.cc (_pinfo::dup_proc_pipe): Can't close proc pipe when
or we will suffer an exit code race.
Even when you will wait for yourself, as a top Cygwin process?
In the same vein, if the last process in a chain is a Windows
process, :exit gets called by the Cygwin parent with norecord, so the
state is not set to PID_EXITED and the logical parent is not alerted.
It's not critical, but it would be easy to make use of the return
value of ciresrv.sync, which could be placed in the P_OVERLAY case.
Also, PID_EXITED is used in the case
(!created && createit && (procinfo->process_state & PID_EXITED)
but it's not a sure way of handling the transient because the new
process may not have access rights to the old pinfo, leading to a
hard failure. To minimize the likelihood of such an event, one could
call myself->release () before ExitProcess.
The order is already optimized in remove_proc.
More information about the Cygwin-developers