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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=RO7hgTkZgzSrll13pG7sAVfBZp7aSk62+hSa4I0t/dyoBkFUdmJRA
	/yW8k22aQ1vmBn1VbJtv170VjcBiQBYSWfgvRLNE4Hsc2vkYJWOntxce01oqmZet
	1RFFigVfxWKjwyeEHjp9cdJFO8O6MICO9+VT6nICRZ2hvlUZ9Z8R7Y=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=rSISe90OVl9xM5I49UaUcZO4pFI=; b=KPjjUEM8jwjqt3bxZmDoNft1FZuj
	izE94ELb0zq46Myr3UgM5LZ0q7IuoZc1h48Tk2Ki/q8hEPLdmVfObT4w/gCwjPLu
	FkWfMxckguRvsum15HavMaDfAxktcT4h6b5ymA9YIK95Y6Ns6LiuasjWJUVBXymk
	4vUlbu5wC1p5y2s=
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=2.5 required=5.0 tests=AWL,BAYES_50,CYGWIN_SUBJECT,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19lnKWKmQSW96ZzbndnB6xN
Date: Thu, 18 Jul 2013 15:15:09 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: confirm subscribe to cygwin-developers-digest AT cygwin DOT com
Message-ID: <20130718191509.GA588@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1374159471 DOT 12713 DOT ezmlm AT cygwin DOT com> <107C24740CC429479D55901D6AAD17E43C536ABB87 AT EMV61-UKRD DOT domain1 DOT systemhost DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <107C24740CC429479D55901D6AAD17E43C536ABB87@EMV61-UKRD.domain1.systemhost.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

[What an odd subject line]
On Thu, Jul 18, 2013 at 04:23:32PM +0100, trefor DOT 2 DOT edwards AT bt DOT com wrote:
>I have a very recent version of Cygwin and using the SIPP application.
>This calls nanosleep from within a thread.

"Very recent" is not a precise enough distinction for debugging
problems.

See: http://cygwin.com/problems.html .

>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.

Seems like a simple test case would show this.  Please provide one.

--
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