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 X-Authenticated: #14308112 Date: Sun, 28 Aug 2005 14:41:45 +0300 From: Pavel Tsekov X-X-Sender: ptsekov@mordor To: cygwin@cygwin.com Subject: Re: zsh: command not found => hangs In-Reply-To: Message-ID: References: <20050823205318.GF6716@bouh.ens-lyon.fr> <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 X-Y-GMX-Trusted: 0 X-IsSubscribed: yes Hello, On Sun, 28 Aug 2005, Pavel Tsekov wrote: > First I determined (by using strace) the place in zsh where the hang > occurs to be in or after zhandler() when it processes SIGCLD. Then I > built debugging zsh and after debugging for a while it turned out that > the hang occures after leaving the signal handler. Some things I forget to mention. zsh is supposed to be sigsuspend-ed at the time the signal handler is executed - this maybe obvious from the backtrace but in any case I mention it. The second thing is that I was able to reproduce this when connected via ssh to the Cygwin machine or when I run zsh in rxvt window but not when in Cygwin console. Maybe pty slows things a bit and that's why the "race" surfaces in these cases. -- 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/