This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

On Tue, Sep 14, 2004 at 02:45:11AM -0400, Bogdan Vacaliuc wrote:
>Chris, Pierre,
>> I was thinking the same thing but AFAIK, ash doesn't have the 
>> pid recycling problem.
>In my failure cases, configure is run under bash.
>I have also captured (finally?) an strace under the ~current cygwin
>(attached).  The details are largely the same as Peter's last
>attachment, to which Igor remarked "FWIW, expr.exe does seem to exit
>with the right exit code, but is later zombified, which doesn't sound
>quite right."
>Actually, its ok for it to be zombified, because the parent didn't
>happen to be waiting for the child at the time that the child exited.
>>>>Pierre's observation that error text is output by the parent shell
>>>>*before* the expr command even executes was an inspiration.
>So it seems like the parent shell decides its going to exit after
>forking but before waiting on the expr process.

That is consistent with the recycled pid problem.  Are you seeing
duplicated pids?

>> Wasn't there a registry value that controlled how pids were 
>> allocated? I can't find anything appropriate in google.
>I looked for something about this in M$ knowledge base.  I didn't find that, but I found this:
>"BUG: Registry access from multiple threads might fail" (WinNT, Win2K)

I don't really see how that applies.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]