Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mcnc!ecsvax!utoddl
From: utoddl@ecsvax.UUCP (Todd M. Lewis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Catching free memory violations
Message-ID: <7417@ecsvax.UUCP>
Date: 31 Jul 89 15:27:52 GMT
References: <7408@ecsvax.UUCP> <694@jc3b21.UUCP>
Organization: UNC Educational Computing Service
Lines: 27

In article <694@jc3b21.UUCP>, fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes:
[...]
> the next chunk pointer to be sure that was zero.  However, any application
> might allocate the memory, write on it, and free it without clearing it.
> So finding non-zero values in free memory wouldn't mean you had discovered
> a program which was writing on memory it didn't own.

Right.  Which is why I plan to SetFunction() FreeMem(), so that I can
zero out any ram that is returned to the free memory pool.
   Thanks.  Any other ideas?  It looks like I'll have a little time
to think about it before I get down to code--My wife is using
the Amiga all the time now for her school work.  Guess I'll have
to buy another Amiga!
> 
> --Fabbian Dufoe
>   350 Ling-A-Mor Terrace South
>   St. Petersburg, Florida  33705
>   813-823-2350
> 
> UUCP: ...uunet!pdn!jc3b21!fgd3


Todd M. Lewis, utoddl@ecsvax.uncecs.edu, utoddl@ecsvax.bitnet
  To quote Eugene H. Spafford, "Crisis and Aftermath", Communications of
  the ACM, vol. 32, no. 6, (June 1989), p. 684:
  "It is curious that this many people [...] would assume to know the
   intent of the author based on the observed behavior of the program."