Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 28 Feb 2001 18:44:17 -0500 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: Memory problem Message-ID: <20010228184417.F5603@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: <230667FC62B4D311BBA90050DA41CFD759D3D9@ddipdc.ddi.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <230667FC62B4D311BBA90050DA41CFD759D3D9@ddipdc.ddi.nl>; from p.boncz@datadistilleries.com on Wed, Feb 28, 2001 at 08:15:23PM +0100 On Wed, Feb 28, 2001 at 08:15:23PM +0100, Peter Boncz wrote: >Christopher, > >Some applications like to make use of so-called "anonymous virtual memory" >for allocating (huge) chunks of memory outside the malloc heap. In unix this >functionality is usually available through mmap()-ing on the special file >/dev/null or thourgh a special mmap() flag. In my application, I abstract >this functionality is a small system-specific library that in my cygnus port >actually directly uses VirtualAlloc(). > >sorry for that. I don't think this has any bearing whatsoever on what the user was doing. He didn't mention that he was using any Windows functions. I think that it is likely that my pointer to "heap_chunk_in_mb" will probably solve his problem if this actually turns out to be an out-of-memory condition. If this is just a simple Windows program, however, maybe he should contact the mingw list. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple