Article View: comp.sys.amiga.tech
Article #705Re: Catching free memory violations
From: Todd M. Lewis
Date: Thu, 03 Aug 1989 14:34
Date: Thu, 03 Aug 1989 14:34
12 lines
950 bytes
950 bytes
In article <SHADOW.89Aug2140114@pawl.rpi.edu>, shadow@pawl.rpi.edu (Deven T. Corzine) writes: > Ah, but interrupts are forbidden to call the memory allocatio > routines, as the system free memory list may well be corrupt. So, > people expect Forbid()/Permit() to work... People also expect FreeMem() to return the memory to the system. FreeMem() can be expected to change the contents of the freed ram (for example, to link it into the free memory list). Think of it as #define TrashThisRAM FreeMem and you'll begin to get my point. -- Todd
Technical Details
Message-ID:
<7426@ecsvax.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!mcnc!ecsvax!utoddlReferences:
<681@lpami.wimsey.bc.ca> <SHADOW.89Aug2140114@pawl.rpi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!mcnc!ecsvax!utoddl From: utoddl@ecsvax.UUCP (Todd M. Lewis) Newsgroups: comp.sys.amiga.tech Subject: Re: Catching free memory violations Message-ID: <7426@ecsvax.UUCP> Date: 3 Aug 89 14:34:48 GMT References: <681@lpami.wimsey.bc.ca> <SHADOW.89Aug2140114@pawl.rpi.edu> Organization: UNC Educational Computing Service Lines: 12