Article View: comp.sys.amiga.tech
Article #655Re: Catching free memory violations
From: Robin Rosenberg INF
Date: Sun, 30 Jul 1989 21:27
Date: Sun, 30 Jul 1989 21:27
15 lines
868 bytes
868 bytes
In article <3985@cps3xx.UUCP>, usenet@cps3xx.UUCP (Usenet file owner) writes: > Forbid(); > FreeMem(x,len); > playsomemore(x); > Permit(); > > No if you go zeroing things out at the FreeMem call, you can potentially > screw somebody up. FreeMem is just that. It gives the memory _back_ to the system which is then free to tag and use the memory anyway it wants to. Using free'd memory is a bad habit. Get rid of it. It does not work. Forbid() doesn't help. ----- Robin Rosenberg
Technical Details
Message-ID:
<148@ra.abo.fi>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!kth!draken!tut!ra!rosenberReferences:
<7408@ecsvax.UUCP> <694@jc3b21.UUCP> <3985@cps3xx.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!kth!draken!tut!ra!rosenber From: rosenber@ra.abo.fi (Robin Rosenberg INF) Newsgroups: comp.sys.amiga.tech Subject: Re: Catching free memory violations Message-ID: <148@ra.abo.fi> Date: 30 Jul 89 21:27:01 GMT References: <7408@ecsvax.UUCP> <694@jc3b21.UUCP> <3985@cps3xx.UUCP> Organization: Abo Academy, Finland Lines: 15