Article View: comp.sys.amiga.tech
Article #697Re: Catching free memory violations
From: Deven T. Corzine
Date: Wed, 02 Aug 1989 18:01
Date: Wed, 02 Aug 1989 18:01
26 lines
1603 bytes
1603 bytes
On 30 Jul 89 22:15:49 GMT, lphillips@lpami.wimsey.bc.ca (Larry Phillips) said: In <SHADOW.89Jul31154235@pawl.rpi.edu>, shadow@pawl.rpi.edu (Deven T. Corzine) writes: Deven> And yet, it IS assumed to be safe, if you're forbidden. (It Deven> *may* even be (semi) officially sanctioned. But I wouldn't Deven> count on it.) Regardless, people *expect* this to work, and it Deven> would help not to break it without needing to. Larry> Why would anyone assume this was a safe thing to do? If you Larry> want to wrap a Disable()/Enable() pair around that, I might be Larry> inclined to consider it semi-safe. 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... Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2214 12th Street, Troy, NY 12180 Phone: (518) 271-0750 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.
Technical Details
Message-ID:
<SHADOW.89Aug2140114@pawl.rpi.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!watmath!att!pacbell!ames!bionet!csd4.milw.wisc.edu!leah!rpi!pawl!shadowReferences:
<681@lpami.wimsey.bc.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!att!pacbell!ames!bionet!csd4.milw.wisc.edu!leah!rpi!pawl!shadow From: shadow@pawl.rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: Catching free memory violations Message-ID: <SHADOW.89Aug2140114@pawl.rpi.edu> Date: 2 Aug 89 18:01:14 GMT References: <681@lpami.wimsey.bc.ca> Sender: usenet@rpi.edu Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 26 In-reply-to: lphillips@lpami.wimsey.bc.ca's message of 30 Jul 89 22:15:49 GMT