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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 27 Feb 2003 11:38:18 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Fabrice Marchal cc: cygwin AT cygwin DOT com Subject: Re: mem allocation / heap_chunk In-Reply-To: <3E5E3A55.2050008@inf.ethz.ch> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 27 Feb 2003, Fabrice Marchal wrote: > Hi, > I have come accross the 384 Mb limit for allocating memory in cygwin. > (e.g. char* pnt = new char[ long size = 500*1024*1024 ]; will not work ) > > I have been able to modify this using the workaround documented in the > Users Guide (http://cygwin.com/cygwin-ug-net/setup-maxmem.html) > > I would like to know if there is a way to do the same within code so > that end-users > who receive a cygwin-compiled code do not require to go into the hassle of > using regtool or regedit > > Is that feasible? > > Thanks > fm Sure. Write a script that uses regtool. Make it a postinstall script, put a "Reboot or restart Cygwin" in the README. It would be more robust if you also check the heap_chunk value before writing to it, in case the user already has it set to something higher. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/