Mail Archives: djgpp/1999/08/24/17:42:09
Dan Gold wrote:
>
> Hey,
>
> I have tested and tested to see if there is still memory allocated after I
> malloc() it and free() it. The result is always yes!. Mayby it's some
> other part of this operation but I've narrowed it down to free(). I just
> wanted to know if anyone else has the same problem, I think there may have
> been a thread earlier about malloc or something in that area having a bug.
> Well if there is a patch or something, could someone let me know?
There is no good way for `free' to return memory to the system for use
by other programs, so it just reserves it to hand out again for future
calls to `malloc'. This is how it works on the vast majority of
systems.
> and
> another thing, when updating to a newer version of gcc and gpp is the only
> thing you have to do unzipping them and replacing the old files...?
This should be safe if you're upgrading *from* v2.8.1 or later. Earlier
versions had a different directory structure which won't be overwritten,
so for them you might want to delete the old files first. (Getting the
fileutils and doing (cd /djgpp; rm @manifest/gccNNN.mft) is a handy way
of doing that.)
--
Nate Eldredge
nate AT cartsys DOT com
- Raw text -