From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31096 invoked by alias); 3 Oct 2005 17:49:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31062 invoked by uid 22791); 3 Oct 2005 17:49:15 -0000 Received: from c-24-61-23-223.hsd1.ma.comcast.net (HELO cgf.cx) (24.61.23.223) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 03 Oct 2005 17:49:15 +0000 Received: by cgf.cx (Postfix, from userid 201) id 4ADB613C101; Mon, 3 Oct 2005 17:49:14 +0000 (UTC) Date: Mon, 03 Oct 2005 17:49:00 -0000 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 X-SW-Source: 2005-10/txt/msg00037.txt.bz2 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/