Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 14 Sep 2005 15:19:22 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: A new day, a new snapshot, more testing required on the road to 1.5.19
Message-ID: <20050914191922.GB23903@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050914170115 DOT GA20659 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: <20050914170115.GA20659@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.8i

On Wed, Sep 14, 2005 at 10:58:56AM -0700, Yitzchak Scott-Thoennes wrote:
>On Tue, Sep 13, 2005 at 06:14:02PM -0400, Christopher Faylor wrote:
>>I'm asking, once again, for people to test the latest cygwin snapshot.
>>The snapshot that is currently available should be very close to an
>>official release of cygwin version 1.5.19.
>
>With either 20050912 or 20050913, trying to start emacs in a console
>window gets:
>
>emacs: Memory exhausted--use M-x save-some-buffers RET
>
>Reverting to 1.5.18 fixed this; cygcheck output is from after reverting
>to 1.5.18.

I could duplicate this.  That's too bad.  I was trying to fix a problem
where fork occasionally gives an annoying error when you hit CTRL-C but
it has a mysterious side effect of causing the above behavior.

The latest 2005-Sep-14 snapshot should "fix" this (I reverted my
change).  Could you confirm that things are working now?

cgf

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