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:	Sat, 20 Jul 2002 01:00:32 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: [bug found] Re: cygwin hang problem
Message-ID:	<20020720050032.GA7816@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<3D32FC00 DOT 5090108 AT hekimian DOT com> <20020719050925 DOT GA24259 AT redhat DOT com> <3D37F0E5 DOT 50F3669B AT yahoo DOT com> <20020719141242 DOT GB27697 AT redhat DOT com> <3D38949C DOT 3090200 AT hekimian DOT com> <3D38C63B DOT 1070201 AT hekimian DOT com> <20020720023006 DOT GB4688 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20020720023006.GB4688@redhat.com>
User-Agent:	Mutt/1.3.23.1i

On Fri, Jul 19, 2002 at 10:30:06PM -0400, Christopher Faylor wrote:
>>So the locking needs some changing in the dll linkage code.  There is
>>in fact a comment above dll_func_load that the code may not be thread
>>safe!
>
>Right.
>
>What two threads are accessing this info simultaneously?  It's probably
>easier to fix that than to introduce locking.

I'd still like to find what threads are simultaneously looking for the
same info but, in the meantime, I've rewritten that particular section
of code so that there is only one memory write, which should be thread
safe.

Does it work any better now?

cgf

- Raw text -