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: Sun, 28 Aug 2005 14:08:45 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: zsh: command not found => hangs Message-ID: <20050828180845.GA24400@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050825001137.GI7338@bouh.ens-lyon.fr> <20050825220454.GR7662@bouh.ens-lyon.fr> <20050826005349.GA4087@trixie.casa.cgf.cx> <20050826191429.GA2034@trixie.casa.cgf.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 Sun, Aug 28, 2005 at 02:28:13PM +0300, Pavel Tsekov wrote: >I did trace this problem an it looks like a race in Cygwin but I may be >wrong. Here I am providing two backtraces from a debug session - the first >one shows what happens normally and the second one shows the hang: I appreciate that you fired up gdb to look into the problem but Cygwin is a multi-threaded application. You need to look at all of the threads if you figure out a potential race. >P.S. While looking at this I noticed that Cygwin's wait family of >functions won't return 0 if WNOHANG is passed and no children are found >that match the wait criteria - JFYI. AFAICT, Cygwin returns 0 in a WNOHANG criteria, just like linux. If you have evidence to the contrary, a simple test case 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/