Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 To: egor duda In-Reply-To: <1033141306.9593.8.camel@lifelesswks> References: <20020925141653 DOT GA6134 AT redhat DOT com> <1033139976 DOT 22908 DOT 333 DOT camel AT lifelesswks> <163544913434 DOT 20020927192540 AT logos-m DOT ru> <1033140780 DOT 9593 DOT 0 DOT camel AT lifelesswks> <1033141306 DOT 9593 DOT 8 DOT camel AT lifelesswks> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-B31hAlejm8xmIYd5GSgu" Date: 28 Sep 2002 01:46:22 +1000 Message-Id: <1033141582.9593.12.camel@lifelesswks> Mime-Version: 1.0 --=-B31hAlejm8xmIYd5GSgu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Gah! Confused myself but good. The pthread::create routine *is* a int returning static method. Sigh. Ok, from the top again.. pthread_create - won't error itself static pthread::create - will EAGAIN if pthread creation fails, and ONLY if pthread creation fails. This uses new pthread() and pthread->create (create params). and a check on object validity after the creation. So my prior email about the logic *is* correct, just not the bit about there being a mistake :]. So, you need to strace the api test to see what's failing. Rob --=-B31hAlejm8xmIYd5GSgu 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) iD8DBQA9lH1OI5+kQ8LJcoIRAt3aAJ0SvF4UPvLnmHjG58qcuc5KxFsPWgCfVH2N lQNMMPEwg12yqdGbTgVeEjY= =SpqU -----END PGP SIGNATURE----- --=-B31hAlejm8xmIYd5GSgu--