Date: Sun, 14 May 2006 18:06:28 -0700
From: clayne AT anodized DOT com
To: cygwin AT cygwin DOT com
Subject: Re: need help with cygwin snapshot debugging
Message-ID: <20060515010627.GJ1783@ns1.anodized.com>
References: <20060510180135 DOT GA8125 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060510180135.GA8125@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, May 10, 2006 at 02:01:35PM -0400, Christopher Faylor wrote:
> There are a few reported problems with the current snapshots that
> require some debugging:
> 
> 1) http://cygwin.com/ml/cygwin/2006-04/msg00718.html
> 
> I would appreciate knowing if anyone can duplicate 1) above and
> I'd like to know if my debugging suggestion in 2) worked.  If you
> can duplicate 1) then any insight into why it is happening would
> be welcome.

While I would say I used to have more fork(): resource not available issues
pre 0313, I also had made changes to my desktop heap settings in the
registry - colluding any of my own efforts to tie in a specific snapshot
as having "fixed" my fork() issues. I still see them *occasionally* but
not nearly as often after having adjusted my desktop heap. However, the
slowness issue in 20060313(+onwards) is extremely prevalent for me currently.

-cl

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