Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Rolf Campbell Subject: Re: bash hang ( G:\Cygwin\bin\find.exe: *** WFSO timed out for after longjmp) Date: Mon, 31 Mar 2003 21:05:25 -0500 Lines: 19 Message-ID: References: <002f01c2f739$580033c0$9a7586d9 AT ellixia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en In-Reply-To: <002f01c2f739$580033c0$9a7586d9@ellixia> Elfyn McBratney wrote: > Hi, > > I've seen this quite a lot of hangs over the last 3-4 months when doing > large find's and it's not always easy reproduce and normally occurs when > find has finished and returned, but not always. If you run the following > from a bash prompt (seen it in cmd.exe and rxvt) and run the following > > $ find /usr/include -name "*.h" -exec fprep "_t" {} \; ^??? > After that has returned if you wait for 30-60 seconds you may see the above > message. If not try a few times, same intervals and it should crop up, but > like I said it's not always easy to reproduce. It's not damaging as a ^C > will break free of it, just wanted to let you know I'm seeing it. :-) It's > coming from sync_with_parent in fork.cc ... Just tried it 5 times, never had any problems... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/