Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Sun, 29 Sep 2002 23:30:01 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Cc: cygwin-developers AT cygwin DOT com
Subject: Re: Many pthread failures in the test suite, one setgroup failure
Message-ID: <20020930033001.GC7906@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>,
	cygwin-developers AT cygwin DOT com
References: <1033264646 DOT 4375 DOT 78 DOT camel AT lifelesswks> <20020929020609 DOT GB11549 AT redhat DOT com> <1033265603 DOT 4374 DOT 95 DOT camel AT lifelesswks> <20020929022338 DOT GA12659 AT redhat DOT com> <1033267203 DOT 4374 DOT 100 DOT camel AT lifelesswks> <20020929024420 DOT GA13416 AT redhat DOT com> <1033271512 DOT 4372 DOT 102 DOT camel AT lifelesswks> <3 DOT 0 DOT 5 DOT 32 DOT 20020929165333 DOT 0080fae0 AT mail DOT attbi DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20020929224948 DOT 00825140 AT h00207811519c DOT ne DOT client2 DOT attbi DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20020929231122 DOT 0082b170 AT h00207811519c DOT ne DOT client2 DOT attbi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3.0.5.32.20020929231122.0082b170@h00207811519c.ne.client2.attbi.com>
User-Agent: Mutt/1.4i

On Sun, Sep 29, 2002 at 11:11:22PM -0400, Pierre A. Humblet wrote:
>At 11:10 PM 9/29/2002 -0400, Christopher Faylor wrote:
>>Hopefully, you've run "make clean" and then "make".  Just to be safe.
>
>I had done that this afternoon, after getting the thread.h change,
>but not tonight.

Ok.  Probably not worth doing after just the thread.cc changes.

FWIW, I'm seeing this now:

"Received a unexpected wait result on mutexInitializationLock -1"

sporadically during builds.

cgf