Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 6 Jul 2005 00:40:39 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Please try latest snapshot -- pthreads mutex users please note Message-ID: <20050706044039.GB24605@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050706022124 DOT GA22020 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Wed, Jul 06, 2005 at 04:17:34AM +0000, Arash Partow wrote: >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. The message that you are replying to mentions a change in the behavior of default mutexes which was made to make cygwin jive with linux. >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... Hmm. If you want to send a "still broken" message every time I ask people to check a snapshot, please feel free. I was trying to tell you when and how it would be useful for you to report problems so that you wouldn't have to bother sending email which was basically a no-op. It's your choice, of course, as to when and how often you choose to send messages but I thought that delineating what was useful and what wasn't would be helpful. 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/