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 Date: Wed, 2 Nov 2005 14:36:20 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Peter Rehley cc: cygwin AT cygwin DOT com Subject: "fork: Resource Temporarily Unavailable" (Was Re: Hang with 1.5.18, 1.5.19 snapshot 20051029) In-Reply-To: <1A1136EA-FBB0-4C01-86D3-BD792EC984E7@rehley.net> Message-ID: References: <34588B2E-B3B4-4B12-A1C2-7D0AD150E475 AT rehley DOT net> <43677321 DOT 9070902 AT scytek DOT de> <1A1136EA-FBB0-4C01-86D3-BD792EC984E7 AT rehley DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 2 Nov 2005, Peter Rehley wrote: > [snip] > One really odd thing that I did notice on my windows 2000 machines was > that when I do a 'ps -ef' many times in a row quickly, the > test_configure script that I'm using dies...it either segfaults or I get > fork: Resource Temporarily unavailable. I've been recently plagued with a "resource temporarily unavailable" (a.k.a. EBUSY) fork problem (on WinXP), with 1.5.18, snapshots, and self-build DLLs. I don't know if it's related to what you're seeing. The problem doesn't seem to be reproducible under gdb, but can be reproduced under strace for long-running scripts. I hereby repeat my plea to Cygwin developers for debugging suggestions -- what information would be useful to put into the strace to help (me) track down the source of this problem? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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/