Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<002f01c2f739$580033c0$9a7586d9@ellixia>
Reply-To:	"Elfyn McBratney" <elfyn AT exposure DOT org DOT uk>
From:	"Elfyn McBratney" <elfyn DOT mcbratney AT exposure DOT org DOT uk>
To:	"cygwin" <cygwin AT cygwin DOT com>
Subject:	bash hang ( G:\Cygwin\bin\find.exe: *** WFSO timed out for after longjmp)
Date:	Mon, 31 Mar 2003 04:55:17 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4910.0300

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 ...




--
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/

- Raw text -