Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!ginosko!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: free behavior (was: Re: Out-of-bounds pointers)
Message-ID: <11254@smoke.BRL.MIL>
Date: 11 Oct 89 06:12:52 GMT
References: <1009@mtxinu.UUCP> <12570028@hpclwjm.HP.COM> <868@crdos1.crd.ge.COM> <217@bbxsda.UUCP> <11234@smoke.BRL.MIL> <17119@rpp386.cactus.org>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 6

In article <17119@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes:
>Doesn't free() insure the pointer remains valid until the next
>call to malloc().

No.  The "guarantee" you cited was repealed long ago.
A free()d pointer is immediately "dead".