X-Spam-Check-By: sourceware.org Date: Tue, 25 Apr 2006 16:39:17 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Call for testing Cygwin snapshot Message-ID: <20060425203917.GB18840@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Tue, Apr 25, 2006 at 04:33:37PM -0400, Ernie Coskrey wrote: >Well, what I got from your message was that you were pretty sure that >your fix may have addressed the problem, but not 100% sure. That's why >I posted this follow-up; it's possible that Jerry has found a scenario >that causes this problem to occur. Maybe not, but if he can reproduce >it it would be worth checking. There are all sorts of "cygwin hang" bug reports out there. Since this is a problem that showed up in a particular snapshot and the problem that you are talking about was something that supposedly happened for any version of cygwin from 2003 to (at least) February 2006, I don't see any reason to think that this is an issue since it would also show up in a pre 2006-03-13 version of cygwin -- unless you have some insight into the problem that I'm missing. 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/