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: Sun, 21 Nov 2004 17:46:48 -0800 From: Lester Ingber To: cygwin AT cygwin DOT com Cc: cygwin-xfree AT cygwin DOT com Subject: Re: new Cygwin has memory problems? / cygwin1-20041117.dll Message-ID: <20041122014648.GA2476@ingber.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cygwin1-20041117.dll, which I got from www.cygwin/snapshots/, solves a few problems, stopping hanging in dired, ispell, and updatedb. (The crash I experienced is getting more common in XP SP2, BAD_POOL_HEADER (www.tweaksforgeek.com/BAD_POOL_HEADER.html)). Lester Christopher Faylor wrote: ------------8<------------ top cut -> bottom ------------->8------------ is is a problem caused by this change: http://cygwin.com/ml/cygwin/2004-10/msg00364.html And, then, the problem was noted here: http://cygwin.com/ml/cygwin/2004-10/msg00904.html The problem is that cygwin is now behaving like linux in that timed reads from a pty/tty work correctly. It is not behaving like linux in that once you get an EOF on a read using stdio, you get EOF forever after. I've made a cygwin-specific correction to the newlib library to make cygwin work more like linux. I will generate a cygwin snapshot sometime soon which should have a fix for this problem. Keep an ey on: http://cygwin.com/snapshots/ cgf ------------8<------------ bottom cut <- top ------------->8------------ -- 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/