Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Mon, 3 Oct 2005 13:49:14 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: on the road to 1.5.19 - snapshot testing needed Message-ID: <20051003174914.GC9307@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050929231320.GA13715@trixie.casa.cgf.cx> <433DEFF6.9050004@scytek.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <433DEFF6.9050004@scytek.de> User-Agent: Mutt/1.5.8i On Fri, Sep 30, 2005 at 10:09:58PM -0400, Volker Quetschke wrote: >P.S.: We (?) will try the next snapshot ASAP, unfortunately this >means in this case on the next weekday (monday). I added new debugging and a new locking mechanism to the latest snapshot. It's possible that the new locking may fix the problem but, if not, then possibly the new debugging will help. Out of curiousity, does your build use procps, fifos, or use the /proc "filesystem" in any way? 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/