Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: how do you know 'free' freed?
Keywords: free, malloc, memory, allocation
Message-ID: <11275@smoke.BRL.MIL>
Date: 14 Oct 89 03:12:04 GMT
References: <5521@hacgate.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 6

In article <5521@hacgate.UUCP> howard@aic.dpl.scg.hac.com (Mike Howard (213)317-5690) writes:
>There must be some way to confirm free.

No, in general free() always works (assuming you have given it a valid
pointer that was malloc()ed) and there is no point in trying to see if
it worked.