Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!mips!apple!fernwood!portal!cup.portal.com!R_Tim_Coslet
From: R_Tim_Coslet@cup.portal.com
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Problem with my C program [a few general hints about malloc
Message-ID: <41734@cup.portal.com>
Date: 27 Apr 91 03:26:42 GMT
References: <1991Apr21.210056.5685@ccu.umanitoba.ca>
  <1991Apr22.014758.3846@wam.umd.edu> <A1422792342@thelake.mn.org>
  <2913@atari.UUCP>
Organization: The Portal System (TM)
Lines: 23

>
>Humph.  TOS 1.4 and upwards have NO PROBLEMS with Malloc that have been
>reported to me.
>
>============================================
>Opinions expressed above do not necessarily	-- Allan Pratt, Atari Corp.
>reflect those of Atari Corp. or anyone else.	  ...ames!atari!apratt
Well, I have TOS 1.4 and made a text editor program called SEDT crash.
When I reported the problem to the author of SEDT he traced it back to
the fact that his library was using Malloc directly for all allocations.
When he changed to a different memory allocation algorithm the problem
went away.

Also I just rewrote the memory allocation algorithm for a Modula-2 I have that
appeared to be using Malloc directly...  a short test program using their
library crashed the computer (2 bombs) after a bit over 800 small allocations.
My rewrite made it to 10000 small allocations (from a single large Malloced
block) with no problems.

                                        R. Tim Coslet

Usenet: R_Tim_Coslet@cup.portal.com             BIX:    r.tim_coslet
California could REALLY use 40 days and 40 nights of rain right now!