Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!dftsrv!chrpserv!seiler
From: seiler@chrpserv.gsfc.nasa.gov (Ed Seiler)
Newsgroups: comp.sys.mac.programmer
Subject: Memory allocation in Think C
Keywords: Think C
Message-ID: <521@dftsrv.gsfc.nasa.gov>
Date: 30 Oct 89 13:08:29 GMT
Sender: news@dftsrv.gsfc.nasa.gov
Reply-To: seiler@chrpserv.gsfc.nasa.gov (Ed Seiler)
Organization: Goddard Space Flight Center
Lines: 13

I seem to be having trouble when requesting blocks of memory using Think C
3.01. Checking things out with the debugger under Multifinder, it seems that
when I make a request using malloc or calloc, the resultant blocks start at
very high memory locations that are way out of the application zone, though
everything seems to indicate that I am indeed in the application zone when
the request is made. If I replace a call of malloc woth a call to NewPtr,
(which is all malloc is supposed to do anyway) it works fine. Are there known
bugs in Think C 3.01 memory allocation? Is there a fix in a newer version of Think C?

Ed Seiler
Goddard Space Flight Center
Greenbelt, MD 20771
seiler@chrpserv.gsfc.nasa.gov