Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 13 Sep 2004 22:25:52 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)
Message-ID:	<20040914022552.GC26109@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<00f401c497cd$a803aec0$0b03a8c0 AT lithium> <015101c49932$e1651850$0b03a8c0 AT lithium> <20040914015428 DOT GA741925 AT hpn5170>
Mime-Version:	1.0
In-Reply-To:	<20040914015428.GA741925@hpn5170>
User-Agent:	Mutt/1.4.1i

On Mon, Sep 13, 2004 at 09:54:29PM -0400, Pierre A. Humblet wrote:
>The surprise is that the error message:
>"configure: error: invalid package name: extra-includes"
>is produced at time 29722848 by bash 2624 (the main script pid).  This
>is BEFORE the second expr is exec'ed.  This occurs only at time
>29725911 by a forked child 2656 of 2624 Following the output of the
>error message, 2624 proceeds to fork 2384, which apparently does
>nothing.  2624 then waits for 2656 and 2384 and exits.
>
>In other words the control flow seems to be seriously screwed up.  It
>may be linked to the pid reuse problem in bash, but I know very little
>about it.  Looking at the full trace available from Peter may help.

I was thinking the same thing but AFAIK, ash doesn't have the pid
recycling problem.

IIRC there is a problem with normal bash where it could be confused by
repeating pids even when the pids are separated by a large number.  It
can even happen on linux.

I will create a snapshot with double the number of pids cached in
cygwin.  This will cause the last 8 pids to be held from reuse by
windows.

Wasn't there a registry value that controlled how pids were allocated?
I can't find anything appropriate in google.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -