Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Subject: Re: pthreads "problem" Re: GDB always receives sigsegv with cygwin
	1.3.13-2
From: Robert Collins <rbcollins AT cygwin DOT com>
To: cygwin AT cygwin DOT com
In-Reply-To: <20021016235405.GA25691@redhat.com>
References: 
	<83040F98B407E6428FEC18AC720F5D732DB730 AT exchange DOT tropicnetworks DOT com> 
	<20021016235405 DOT GA25691 AT redhat DOT com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-rZqr8FPeg3HGaaN0Z91d"
Date: 17 Oct 2002 10:07:50 +1000
Message-Id: <1034813270.8144.1.camel@lifelesswks>
Mime-Version: 1.0

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

On Thu, 2002-10-17 at 09:54, Christopher Faylor wrote:
> On Wed, Oct 16, 2002 at 07:07:16PM -0400, Rolf Campbell wrote:

> Robert Collins, can this behavior be changed?  Can we avoid checking
> PTHREAD_MUTEX_INITIALIZER for validity.  I think you may have done this
> once before, in fact.

Christopher Faylor,
I don't think we can. I will look into it today / tomorrow though. We
*may* be able to change the order of the test.

Rob
--=20
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

--=-rZqr8FPeg3HGaaN0Z91d
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)

iD8DBQA9rf9VI5+kQ8LJcoIRAjiqAKCNIMgRHMdwrHM1NxR8mU8c+RVidgCguP21
/e5cKc49gGoox7vh0TJpRpA=
=WyUO
-----END PGP SIGNATURE-----

--=-rZqr8FPeg3HGaaN0Z91d--