X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=MHsdcVsXxLjdlpGVM9oo4ZUT7KYxs
	0g+PHfZT/SzjY9zbSiXxbL1Ae3RmOmYxosG/GQMST6sfZ/Y8mXD+B6tDG++QRZf/
	v4lrHbYTdtnDk7FrocZcEloOA6gB+bEbksKgh/LK7tzRDIJoaxsrq35RaldBEdB8
	1ClsdYNwjrPV0c=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=r8V87NoK5hoI8gexlz6C0ZTGXqg=; b=i5G
	zpxHMwuXBCtdL+8j1GGqa7sSnoxwf+ubMvwrFbTxIzwdJtvZwcLYKmdbNbH6eZuP
	Hd/hscrWKf+NPAue9syZzGkyfikmgawFbivy/GZE2eTjPXv6pj8OSEbxOvVLoynD
	MtPuMZknDUe9P99f/TiWW7TRLtTrXN9D0knNbED4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
X-Spam-SWARE-Status: No, score=4.0 required=5.0 tests=AWL,BAYES_50,CYGWIN_SUBJECT,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_PASS autolearn=no version=3.3.1
From: <trefor DOT 2 DOT edwards AT bt DOT com>
To: <cygwin AT cygwin DOT com>
Date: Thu, 18 Jul 2013 16:23:32 +0100
Subject: RE: confirm subscribe to cygwin-developers-digest AT cygwin DOT com
Message-ID: <107C24740CC429479D55901D6AAD17E43C536ABB87@EMV61-UKRD.domain1.systemhost.net>
References: <1374159471 DOT 12713 DOT ezmlm AT cygwin DOT com>
In-Reply-To: <1374159471.12713.ezmlm@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id r6IFNwbA015980

I have a very recent version of Cygwin and using the SIPP application. This calls nanosleep from within a thread.

Effectively , every second, the application

*         Creates a thread

*         Calls nanosleep 9 times.

*         Deletes the thread

And every second, according to windows task manager, it one more handle is being used. Eventually it runs out of resources and crashes.

If I comment out the call to nanosleep, the number of handles stay steady.

If the problem was just within nanosleep, the I would expect it to "leak" 9 handles every second, but it only one is leaked. So I'm assuming that it somehow. It's a combination of the thread and the calls to nanosleep.

Hence my question, is nanosleep thread safe?

Regards
Trefor Edwards 

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