X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 26 Oct 2009 13:26:22 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: How to increase the memory available to diff in cygwin 1.7? Message-ID: <20091026172622.GB790@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, Oct 26, 2009 at 11:41:13AM -0400, Kenneth Chiu wrote: >I'm trying to diff two large directories, recursively, and >I'm getting this error: > > $ diff -rq B B2 >diff.out > diff: memory exhausted > >I looked at this URL > > http://cygwin.com/cygwin-ug-net/setup-maxmem.html > >but it seemed out-of-date. There was no such key in the >registry, and the options to the regtool were different from >what the regtool man page says. > >Any suggestions on how to get rid of the memory >exhaustion error? Is there a new key path that I should >use for the heap_chunk_in_mb value? Is it possible >that I'm simply bumping into a 2 GB limit for >32-bit processes? (And if that is the case, >is there a recommended way to go to 64-bit?) AFAIK, this is just a limitation of diff. You can get the same error on linux. This was discussed in some detail in this list a few months ago. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple