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
Subject: Re: Many pthread failures in the test suite, one setgroup failure
From: Robert Collins <rbcollins AT cygwin DOT com>
To: cygwin-developers AT cygwin DOT com
In-Reply-To: <20020929185604.GA25789@redhat.com>
References: <20020929000215 DOT GB10872 AT redhat DOT com>
	<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> <20020929141659 DOT GA23836 AT redhat DOT com>
	<1033309085 DOT 11273 DOT 69 DOT camel AT lifelesswks>  <20020929185604 DOT GA25789 AT redhat DOT com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-Jx0bAoYil52th9xOp1Cw"
Date: 30 Sep 2002 08:35:53 +1000
Message-Id: <1033338954.11275.155.camel@lifelesswks>
Mime-Version: 1.0


--=-Jx0bAoYil52th9xOp1Cw
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2002-09-30 at 04:56, Christopher Faylor wrote:
=20
> I couldn't quite catch what was setting the EINVAL, for some reason,
> though.  I rebuilt the DLL with debugging and set some breakpoints on
> likely "return EINVAL"s but they didn't get hit in this context.
>=20
> I did see an occasional EINVAL, though, and it seemed to be happening at
> __pthread_cond_dowait here:
>=20
>   if (!pthread_mutex::isGoodObject (themutex))
>     return EINVAL;
>=20
> I couldn't tell if this was the result of a debugging artifact or if
> it was an actual problem but in this context themutex =3D=3D cond, which
> certainly seems wrong.

I can't see how that would happen from the source, unless cond=3D=3Dmutex a=
t
program entry, which should -never- happend.
=20
> This is unfortunately just speculation so far since I haven't been
> able to catch what's going on.  It does seem to be timing related
> since stopping and single stepping often seems to cause the program
> to "just work".
>=20
> Anyway, that's my current brain dump.

Thanks for that, I'm still stuck doing only a code review :[
,
Rob
--=20
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

--=-Jx0bAoYil52th9xOp1Cw
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9l4BJI5+kQ8LJcoIRApjMAJ95YZtIdbLZZmffhJDk2GR/3Vb5mACeKPoI
lRlRZ7URdk4xO2cSTX0Ai6g=
=vfZ/
-----END PGP SIGNATURE-----

--=-Jx0bAoYil52th9xOp1Cw--