Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Message-ID:	<4312DF32.7080506@vihmapuu.ee>
Date:	Mon, 29 Aug 2005 13:10:58 +0300
From:	Raul Metsma <raul AT vihmapuu DOT ee>
User-Agent:	Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems with Windows threads and cygwin sleep()
References:	<Pine DOT LNX DOT 4 DOT 62 DOT 0508241458460 DOT 26825 AT ns DOT pyerotechnics DOT com> <430D688D DOT 1070205 AT vihmapuu DOT ee> <Pine DOT CYG DOT 4 DOT 58 DOT 0508251054550 DOT 1272 AT mordor> <430D8FC8 DOT 8090906 AT vihmapuu DOT ee> <20050825100234 DOT GL17452 AT calimero DOT vinschen DOT de> <430DA017 DOT 5000402 AT vihmapuu DOT ee> <20050825115019 DOT GP17452 AT calimero DOT vinschen DOT de> <Pine DOT CYG DOT 4 DOT 58 DOT 0508251456520 DOT 2676 AT mordor> <20050825120922 DOT GQ17452 AT calimero DOT vinschen DOT de> <Pine DOT CYG DOT 4 DOT 58 DOT 0508251532350 DOT 2968 AT mordor> <20050825131402 DOT GR17452 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20050825131402.GR17452@calimero.vinschen.de>
X-IsSubscribed:	yes

  > No, I tested with just two cmd windows.  The joke is that I don't see
> the Cygwin process doing anything suspicious.  In my test I just started
> tcsh under strace to see if it begins to behave weird when the threads
> application is running, but it just waits in ready_for_read for user input.
> Nevertheless, threads takes the CPU time when the no. of threads is big
> enough and returns to normal when the Cygwin process stops.  I tried a
> few things but no luck so far.  Maybe Dave is right.
> 

Some more testing

When I comment out signals.cc nanosleep() content and add there
directly windows Sleep() call, then does not occur this issue.
Could this be nanosleep() bug or something deeper?

Raul Metsma

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -