Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 5 Jul 2005 22:21:24 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Please try latest snapshot -- pthreads mutex users please note
Message-ID: <20050706022124.GA22020@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <BAY107-F307C877027AAD7DFDBEBBD6D90@phx.gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BAY107-F307C877027AAD7DFDBEBBD6D90@phx.gbl>
User-Agent: Mutt/1.5.8i

On Wed, Jul 06, 2005 at 01:36:54AM +0000, Arash Partow wrote:
>I've done a clean install of cygwin with dll 1.5.18 and also tried
>snapshots from 2nd, 4th and 5th. Unfortunetly issues relating to
>threading and memory leaks as described in the following post - still 
>exists:
>
>http://sources.redhat.com/ml/cygwin/2005-06/msg00186.html

Right.  I made no effort to fix anything since, I'm not going to try to
debug a 308K application for alleged memory leaks and, AFAIK, Corinna
didn't look into this either.  I guess I implied that previously but
didn't make that clear.

You can assume that unless someone mentions that they've fixed some kind
of memory leak issue, there will be no improvement in the situation that
you've noted so, there's not need to send "it still doesn't work" mail
here.

OTOH, if things get better or worse that is interesting and worthy of
raising a flag.

cgf

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

