Re: Oh man is this a bad one...

From: Jeremy Elson (
Date: 05/09/96

> well, free()ing ch should kill all memory of it, right? 5 mins later if I
> check a pointer I set to the ch before I freed it, it still had the mobs
> stats. It doesnt seem to be getting free'd. That's my main problem.

As someone else has noted, free()ing memory does not explicitly *do* anything
to the memory - it just makes it available for future allocation.  It isn't
necessarily cleared.  (But, if you've free()d it, you shouldn't be looking
at it in the first place to see if it's been cleared or not..)


This archive was generated by hypermail 2b30 : 12/18/00 PST