From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16203 invoked by alias); 18 Jul 2013 15:23:44 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 16193 invoked by uid 89); 18 Jul 2013 15:23:43 -0000 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 Received: from Unknown (HELO smtpe1.intersmtp.com) (62.239.224.234) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 18 Jul 2013 15:23:43 +0000 Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.298.1; Thu, 18 Jul 2013 16:23:34 +0100 Received: from EMV61-UKRD.domain1.systemhost.net ([169.254.2.129]) by EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi; Thu, 18 Jul 2013 16:23:34 +0100 From: To: Date: Fri, 19 Jul 2013 01:47:00 -0000 Subject: RE: confirm subscribe to cygwin-developers-digest@cygwin.com Message-ID: <107C24740CC429479D55901D6AAD17E43C536ABB87@EMV61-UKRD.domain1.systemhost.net> References: <1374159471.12713.ezmlm@cygwin.com> In-Reply-To: <1374159471.12713.ezmlm@cygwin.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2013-07/txt/msg00381.txt.bz2 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 s= omehow. It's a combination of the thread and the calls to nanosleep. Hence my question, is nanosleep thread safe? Regards Trefor Edwards=20 -- 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