X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 11 Oct 2008 00:45:47 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Problem to open big selfextracting Zip files from bash - starting from scratch :-) Message-ID: <20081011044547.GA15280@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5E25AF06EFB9EA4A87C19BC98F5C875301A4DAB3@core-email.int.ascribe.com> <48EE2793.8000901@oracle.com> <31DDB7BE4BF41D4888D41709C476B6570929B539@NIHCESMLBX5.nih.gov> <48EF221A.7010505@oracle.com> <31DDB7BE4BF41D4888D41709C476B6570929B54F@NIHCESMLBX5.nih.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <31DDB7BE4BF41D4888D41709C476B6570929B54F@NIHCESMLBX5.nih.gov> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Oct 10, 2008 at 07:03:26PM -0400, Buchbinder, Barry (NIH/NIAID) [E] wrote: >Speaking of "Changing Cygwin's Maximum Memory" > ... > >Curiously (since I've never played with heap_chunk_in_mb), when I tried >max_memory.exe I got the exact same result as you did. > 5fffe000 bytes (1536.0Mb) >So I recompiled it with the much-reviled-and-soon-to-be-eliminated >-mno-cygwin flag. Interestingly, the result was different. > 77ffe000 bytes (1920.0Mb) Cygwin uses Doug Lea's malloc implementation which can allocate discontiguously so the example in the abovementioned URL is wrong. It does not reflect the largest chunk of memory that could be allocated, which is what heap_chunk_in_mb controls. 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/