Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!xylogics!bu.edu!dartvax!eleazar.dartmouth.edu!watt
From: watt@eleazar.dartmouth.edu (Gill Watt)
Newsgroups: comp.sys.mac.programmer
Subject: ROM bug->ThinkC malloc weirdness
Summary: see subj
Keywords: MMInit ThinkC bug malloc
Message-ID: <1991Feb27.000321.13016@dartvax.dartmouth.edu>
Date: 27 Feb 91 00:03:21 GMT
Sender: news@dartvax.dartmouth.edu (The News Manager)
Distribution: comp
Organization: Dartmouth College, Hanover, NH
Lines: 30


howdy,

I just read about the Memory Manager bug in the 
Feb 26 MacWeek ("Ask David Ramsey") and I got a 
copy of the MMInit patch.  So far, the performance 
improvement has been great (~4x).

My code allocates (using ThinkC's malloc() call for
UNIX portability) approximately 4 Megs during a 
standard run.  
	
I have done a substantial amount of profiling on the 
code and have just noticed a strange thing:

When I run the code from within the ThinkC development
environment, the malloc portion of the code requires
about 1/2 the time that it requires when I run it as
a standalone application.  The execution time of the 
rest of the code is constant. 

Does anyone know why this happens?  

Thanks,

-- 
---------------------------------------------------------------------
Gill Watt (watt@eleazar.dartmouth.edu)
Thayer School of Engineering, Dartmouth College, Hanover, NH  03755
---------------------------------------------------------------------