Article View: comp.sys.amiga.tech
Article #648Re: Catching free memory violations
From: Usenet file owner
Date: Sun, 30 Jul 1989 17:48
Date: Sun, 30 Jul 1989 17:48
31 lines
1248 bytes
1248 bytes
In article <SHADOW.89Jul29071247@pawl.rpi.edu> shadow@pawl.rpi.edu (Deven T. Corzine) writes:
>
>On 28 Jul 89 19:44:05 GMT,
>fgd3@jc3b21.UUCP (Fabbian G. Dufoe) said:
>
>FGD> In article <7408@ecsvax.UUCP> utoddl@ecsvax.UUCP (Todd M. Lewis)
[ --stuff ]
>FreeMem() function to zero memory *as it is freed*. Then either a
>SetFunction()ed AllocMem() function or some separate task/function
There is a sticky problem with this idea,
function() {
x=AllocMem()
playwithit(x);
Forbid();
FreeMem(x,len);
playsomemore(x);
Permit();
}
No if you go zeroing things out at the FreeMem call, you can potentially
screw somebody up.
When a task is ending, does the Tasks memory get freed before
it actually returns?
REAL NAME: Joe Porkka jap@frith.cl.msu.edu
Technical Details
Message-ID:
<3985@cps3xx.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!ginosko!husc6!mailrus!ncar!tank!eecae!cps3xx!usenetReferences:
<7408@ecsvax.UUCP> <694@jc3b21.UUCP> <SHADOW.89Jul29071247@pawl.rpi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ginosko!husc6!mailrus!ncar!tank!eecae!cps3xx!usenet From: usenet@cps3xx.UUCP (Usenet file owner) Newsgroups: comp.sys.amiga.tech Subject: Re: Catching free memory violations Message-ID: <3985@cps3xx.UUCP> Date: 30 Jul 89 17:48:54 GMT References: <7408@ecsvax.UUCP> <694@jc3b21.UUCP> <SHADOW.89Jul29071247@pawl.rpi.edu> Reply-To: porkka@frith.UUCP (Joe Porkka) Organization: Michigan State University Lines: 31