Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <BAY107-F29728D71F3BF5146FCC2B1D6D90@phx.gbl>
X-Originating-Email: [arashp AT hotmail DOT com]
X-Sender: arashp AT hotmail DOT com
In-Reply-To: <20050706022124.GA22020@trixie.casa.cgf.cx>
From: "Arash Partow" <arashp AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Please try latest snapshot -- pthreads mutex users please note
Date: Wed, 06 Jul 2005 04:17:34 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-IsSubscribed: yes

Hi Chris,

Actually things are getting slightly worse, basically same test scenario
(not the full blown app you keep on mentioning), but this time mutex
locks are failing + the ye-olde massive memory leaks.

I have the mutex set to default mode, and after a few seconds of the
test running mutexes locking unlocking, all of a sudden the mutexes
stop locking, and basically report back EBUSY from pthread_mutex_lock.

I know you weren't going to bother looking into it, but seeing as though
you made a general request for testing updates relating to the new dll
version, I thought it useful and relevant to put in my two cents.

maybe in the future I wont even do that...


Regards


Arash Partow
__________________________________________________
Be one who knows what they don't know,
Instead of being one who knows not what they don't know,
Thinking they know everything about all things.
http://www.partow.net



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



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