At 12:25 AM 12/24/2004 -0500, Christopher Faylor wrote:
>On Thu, Dec 23, 2004 at 11:59:59PM -0500, Pierre A. Humblet wrote:
>>At 11:35 PM 12/23/2004 -0500, Christopher Faylor wrote:
>>>I don't think you need it. You just need to tell a process which is
>>>about to exec after having been execed to make sure that its
>>>wr_proc_pipe is valid.
>>
>>Yes, that's the key. So the question is only about method. Either the parent
>>guarantees that the child has a valid handle, or the child must check
>>that it already has a valid handle or wait until it does.
>
>I have just implemented code which causes an execed child to wait for the
>parent to fill in its wr_proc_pipe if it is going to exec again. It uses
>a busy loop but I think it's unlikely that the loop will be exercised too
>often.
It's late, but I am trying to go through all permutations.
Here is a strange one.
Cygwin process A started from Windows execs a Windows process B.
We are in the case where A
if (!myself->wr_proc_pipe)
{
myself.remember (true);
wait_for_myself = true;
The problem is that later there is
if (wait_for_myself)
waitpid (myself->pid, &res, 0);
else
ciresrv.sync (myself, INFINITE);
Process A takes the first branch (waitpid), although it's the
second branch that will call GetExitCodeProcess.
So A will see its logical self terminate, but it won't get the
exit status of B.
Right? Going to sleep on this.
Pierre
