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
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)
Date: Tue, 14 Sep 2004 08:11:39 +0200
Message-ID: <90459864DAD67D43BDD3D517DEFC2F7D7114@axon.Axentia.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Peter Ekberg" <peda AT axentia DOT se>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i8E6Bsd7025821

Christopher Faylor wrote:

> 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 forgot I had that trace and accidentally deleted it. However, creating
a new one is not difficult, so one is available at:
http://www.lysator.liu.se/~peda/bashstrace.bz2

This one is created with "strace -o ..." as suggested by Igor.

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

Don't know where ash comes into play, the script is executed by bash. I
must have missed some other test case...

Cheers,
Peter

--
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/