Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: fix cond_race... was RE: src/winsup/cygwin ChangeLog thread.cc thread.h ...
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4417.0
Date:	Thu, 25 Oct 2001 14:20:37 +1000
Message-ID:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF7A42@itdomain002.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	fix cond_race... was RE: src/winsup/cygwin ChangeLog thread.cc thread.h ...
Thread-Index:	AcFc71WYHXET1T3bTFikwePvJ1mipQAHKJEA
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Jason Tishler" <jason AT tishler DOT net>
Cc:	<cygwin-developers AT sourceware DOT cygnus DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id f9P4Cho24097

> -----Original Message-----
> From: Jason Tishler [mailto:jason AT tishler DOT net]
> Sent: Thursday, October 25, 2001 10:47 AM
> To: Robert Collins
> Cc: cygwin-developers AT sourceware DOT cygnus DOT com
> Subject: Re: fix cond_race... was RE: src/winsup/cygwin ChangeLog
> thread.cc thread.h ...
> 
> 
> Rob,
> 
> On Mon, Oct 22, 2001 at 12:52:14PM +1000, Robert Collins wrote:
> > right, then try sleep (1) where I have 0 :}
> 
> AFAICT, the test case still hangs in the same place or takes 
> a really long
> time to complete.  Even if I try to be tricky (like the aforementioned
> Python code) and alternate between Sleep(0) and Sleep(1).
> 
> Any other ideas?

Add logging code (such as system_printf to the TimedWait method
immediately before the WFSO call. Add similar code to the Signal method
immediately before the PulseEvent.

The log detail should include the thread id (I _think_ thread_printf
includes this and logs to strace) and a timestamp. 

Process the log file to show both events, in time order, and see if
naything pops out. If not forward me the log. 

Do you have sshd on your machine? Or can you bzip2 and mail me a
build+source tree that shows this symptom and is ready-to-go?

Rob

- Raw text -