Path: utzoo!utgpu!watserv1!ria!uwovax.uwo.ca!7103_2622
From: 7103_2622@uwovax.uwo.ca (Eric Smith)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: g++ Part comment, part question.
Message-ID: <1991Feb28.133252.8714@uwovax.uwo.ca>
Date: 28 Feb 91 18:32:52 GMT
References: <10745@jarthur.Claremont.EDU> <GJH.91Feb11103129@ghiggins.hpl.hp.com><1991Feb1 <ENTROPY.91Feb26154539@wookumz.ai.mit.edu>
Lines: 14

In article <ENTROPY.91Feb26154539@wookumz.ai.mit.edu>, entropy@ai.mit.edu (entropy) writes:
> 
> By the way, has anyone noticed that certain programs (such as the CPM
> emulator) completely ignore 'limit' and snarf all of memory anyway?
> 
There are two different flags for limiting memory: -M and -m. One of
them (I forget which) limits the amount of memory the process can Malloc;
the other limits the total amount of memory the process can have.
Some programs never use Malloc or Mshrink; they just keep all the memory
they're given on startup -- for them, you have to use the latter flag.
-- 
Eric R. Smith                     email:
Dept. of Mathematics            eric.smith@uwo.ca
University of Western Ontario   7103_2622@uwovax.bitnet