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 Message-ID: <3E5E3A55.2050008@inf.ethz.ch> Date: Thu, 27 Feb 2003 17:18:29 +0100 From: Fabrice Marchal User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: mem allocation / heap_chunk Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 -- ======================================================================== Fabrice Marchal http://www.inf.ethz.ch/~fmarchal fabrice DOT marchal AT ieee DOT org fmarchal AT inf DOT ethz DOT ch +41-(0)1-632-56-79 ETH Zurich, Computational Science and Engineering FAX:+41-(0)1-632-17-03 ======================================================================== -- 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/