Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!stanford.edu!leland.Stanford.EDU!elaine37.Stanford.EDU!jsk
From: jsk@elaine37.Stanford.EDU (Jeffrey Kuskin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think Pascal/Think C/System 7
Message-ID: <1991May13.213541.6964@leland.Stanford.EDU>
Date: 13 May 91 21:35:41 GMT
References: <53400@nigel.ee.udel.edu> <1991May13.092550.21150@lynx.CS.ORST.EDU> <1991May13.173429.12897@world.std.com>
Sender: news@leland.Stanford.EDU (Mr News)
Organization: Stanford University - AIR
Lines: 20


I applied the 4.0.5 patch and started using the new debugger on some code
I had been debugging with version 4.0.2.  However, after only a few minutes
and only about 75 "step" or "trace" commands, the debugger put up an alert
saying it was critically low on memory.  This never happened to me with
the 4.0.2 debugger, and the code was the same.  The code has no recursion
or other mempry-eating features.  In fact, the call chain is never more
than 4 functions deep and I was displaying only about 10 variables.  
I have since reverted to the 4.0.2 debugger.

Has anyone else encountered these symptoms?  

System:  IIcx, 5mb, 6.0.4



--
Jeff Kuskin
Stanford University
jsk@leland.stanford.edu