Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!uvaarpa!mcnc!rti!xyzzy!meissner From: meissner@dg-rtp.dg.com (Michael Meissner) Newsgroups: comp.std.c Subject: Re: Out-of-bounds pointers Message-ID: Date: 14 Oct 89 16:45:00 GMT References: <1009@mtxinu.UUCP> <12570028@hpclwjm.HP.COM> <868@crdos1.crd.ge.COM> <217@bbxsda.UUCP> <1989Oct7.131404.656@jarvis.csri.toronto.edu> <220@bbxsda.UUCP> <1989Oct10.163732.3241@jarvis.csri.toronto.edu> <240@bbxsda.UUCP> Sender: usenet@xyzzy.UUCP Organization: Data General (Languages @ Research Triangle Park, NC.) Lines: 12 In-reply-to: scott@bbxsda.UUCP's message of 11 Oct 89 15:37:37 GMT In article <240@bbxsda.UUCP> scott@bbxsda.UUCP (Scott Amspoker) writes: > Since free() is probably the only possible way for a *valid* pointer to > suddenly become *invalid* there are some interesting possibilities. Another possible way for a *valid* pointer to suddenly become *invalid* is if the pointer points to automatic storage and you exit the function creating the storage with either a return or a longjmp. -- Michael Meissner, Data General. If compiles where much Uucp: ...!mcnc!rti!xyzzy!meissner faster, when would we Internet: meissner@dg-rtp.DG.COM have time for netnews?