X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48ED154E.2040708@xs4all.nl> Date: Wed, 08 Oct 2008 22:17:18 +0200 From: Bob van Loosen User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Memory leak with timer References: <48EBDDF4.20503@xs4all.nl> <20081007232949.GA13962@ednor.casa.cgf.cx> <48EC02C3.9080403@xs4all.nl> <20081008020850.GA28332@ednor.casa.cgf.cx> In-Reply-To: <20081008020850.GA28332@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Christopher Faylor wrote: > On Wed, Oct 08, 2008 at 02:45:55AM +0200, Bob van Loosen wrote: > >> Christopher Faylor wrote: >> >>> This should be fixed in the next snapshot. If you are looking for a >>> workaround, specifically set the sigev_notify_attributes to >>> PTHREAD_CREATE_DETACHED. >>> >> Thanks, that fixed it. >> Shouldn't PTHREAD_CREATE_DETACHED be default? That's what the opengroup.org >> site says. >> > > Maybe you need to reinvestigate the meaning of "fixed" and "workaround"? From my point of view, the workaround fixed the memory leak. -- 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/