Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Subject: Re: Re: WFSO timed out after longjmp, data pass 3 failed
From: Dirk Reiners <dreiners AT iastate DOT edu>
To: cygwin AT cygwin DOT com
Content-Type: text/plain
Date: Fri, 12 Aug 2005 13:41:35 -0500
Message-Id: <1123872095.29426.303.camel@sandman.vrac.iastate.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


	Hi Brian,

thanks for the explanation, it makes a lot more sense now. 

Yes, the system is very busy. This is running on VMWare, and while the
doxygen is running there is a compiler or two running in the virtual
machine at the same time. In addition to that the doxygen process gets
pretty big (> 250 MB), so copying everything over might take a little
while. 5 minutes seems seriously excessive, but I guess I could hit that
limit if a lot of the main process's memory has gone into swap, and if
the Linux build (which is running on the main system) takes longer than
it should and runs into the VMWare build's time slot. So yes it is a
stretch, but in my situation I could actually see it happen.

I'll look into lightening the load on the system and give the doxygen a
little more processor time.

Thanks a bunch

	Dirk





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