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: <1991Mar1.165908.8721@uwovax.uwo.ca> Date: 1 Mar 91 21:59:08 GMT References: <10745@jarthur.Claremont.EDU> <1991Feb1 Lines: 24 In article , entropy@ai.mit.edu (entropy) writes: > In article <1991Feb28.133252.8714@uwovax.uwo.ca> 7103_2622@uwovax.uwo.ca (Eric Smith) writes: > 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. > > Please, Eric, give me some credit (I do know how to RTFM if nothing > else). I've tried both flags independently and in conjunction and > neither has any effect on the CP/M emulator. No offence intended -- lots of people (myself included) sometimes overlook things in the FM even when they read it. I'm puzzled that the CP/M emulator ignores limit; does it otherwise work OK under MiNT (i.e. can you run it in the background and not have it interfering with other programs)? It's quite possible that, as you suggest, it simply uses all of memory without going through the OS; but in that case it probably will trash any other programs running at the time. Alternatively, there very well could be a bug in MiNT. (heaven forbid :-). -- Eric R. Smith email: Dept. of Mathematics eric.smith@uwo.ca University of Western Ontario 7103_2622@uwovax.bitnet