Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rosen
From: rosen@cs.utexas.edu (Eric Carl Rosen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C malloc()
Summary: Problem solved!
Keywords: malloc THINK_C
Message-ID: <1147@priddy.cs.utexas.edu>
Date: 27 Feb 91 01:00:15 GMT
References: <1145@yoakum.cs.utexas.edu>
Organization: Dept of Computer Sciences, UTexas, Austin
Lines: 8

With the help of two suggestions, I found my problem. It indeed was with MY
code; I had overstepped the bounds of my allocated block by 20 bytes, zeroing
this positions. This corrupted malloc()'s internal pool storage mechanism.

Although many of the replies I received included skepticism about malloc(),
I'm glad to find that, in my experience, malloc() remains reliable.

--Eric