X-Spam-Check-By: sourceware.org
Date: Wed, 21 Dec 2005 19:44:55 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Please try a snapshot - final push for 1.5.19
In-Reply-To: <20051222003056.GB24185@trixie.casa.cgf.cx>
Message-ID: <Pine.GSO.4.63.0512211940560.8494@slinky.cs.nyu.edu>
References: <20051221162249 DOT GA9890 AT trixie DOT casa DOT cgf DOT cx>  <Pine DOT GSO DOT 4 DOT 63 DOT 0512211200200 DOT 8494 AT slinky DOT cs DOT nyu DOT edu> <20051221200117 DOT GA5691 AT panix DOT com>  <20051222003056 DOT GB24185 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Wed, 21 Dec 2005, Christopher Faylor wrote:

> On Wed, Dec 21, 2005 at 03:01:17PM -0500, David Arnstein wrote:
> >On Wed, Dec 21, 2005 at 12:17:09PM -0500, Igor Pechtchanski wrote:
> >> I've been having problems with "fork: resource unavailable" on my machine
> >> with the 10/03 snapshot.  The problem is only reproducible after Cygwin
> >> has been running for a while, under a heavy load.  I'll try to see if it
> >> appears under the 12/20 snapshot, but there's no guarantee I'll be able to
> >> reproduce it in time for the release.  I know this isn't much of a bug
> >> report, but this is just a heads-up.
> >
> >I have been plagued by this problem for monthes now. I don't have a
> >solution, but here is a bash shell script that will reproduce the
> >problem. It is checking every file in its argument list. It is most
> >likely to cause the problem when presented with a long argument list.
> >I like to exercise it by launching it from C:\Windows as
> >	undupe.sh *
>
> Wow.  Two replies to my request for testing the current snapshot.  The
> first talks about a two-month old snapshot and the second doesn't
> provide any details about whether this is a problem with the current
> snapshot or not.
>
> Not what I'd call an auspicious start.

Okay, I was wrong.  I did reproduce the problem with essentially the same
strace under the 12/20 snapshot (sorry, still not the latest, but I'm
building a debug version of cygwin1.dll from cvs HEAD now).  More details
when I have them.
	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!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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