🚀 go-pugleaf

In article <811549923.10778@contech.demon.co.uk>, sbehrens@contech.demon.co.uk (Soenke Behrens) writes:
>jimh@earth.execpc.com (Jim Hennessy) wrote:
>
>>Does the C standard guarantee that storage allocated by malloc() is
>>freed during program termination?  If so, where?  I can't find it.
>
>Nope, this is not guaranteed. You _have_ to free all allocated memory
>yourself. A good strategy would be to work out (before you start coding)
>who is allowed to allocate memory, and who frees it again. A tool like
>memcheck does wonders, too.

This is silly. Free() doesn't guarantee that the storage is returned to the
operating system either. It just makes it available for further mallocs by the
program. If an operating reclaims storage used by a process, it won't matter
whether malloc tables internal to the process have that storage marked as
available or in-use. And if it doesn't reclaim storage, calling free() isn't
going to help.

It's an OS issue.

--

Chris Volpe				Phone: (518) 387-7766 (Dial Comm 8*833
GE Corporate R&D			Fax:   (518) 387-6560
PO Box 8, Schenectady, NY 12301		Email: volpecr@crd.ge.com