Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!cernvax!chx400!chx400!bernina!neptune!c!mneerach
From: mneerach@iiic.ethz.ch (Matthias Ulrich Neeracher)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock Function List
Message-ID: <25830@neptune.inf.ethz.ch>
Date: 21 Feb 91 14:02:13 GMT
References: <1991Feb20.042807.12553@ux1.cso.uiuc.edu> <6484@skye.cs.ed.ac.uk>
Sender: news@neptune.inf.ethz.ch
Reply-To: mneerach@iiic.ethz.ch
Organization: Departement Informatik, ETH, Zurich
Lines: 18

In article <6484@skye.cs.ed.ac.uk>, nick@cs.edinburgh.ac.uk (Nick Rothwell) writes:
>In article <1991Feb20.042807.12553@ux1.cso.uiuc.edu>, dmmg1176@uxa.cso.uiuc.edu (David M Marcovitz) writes:
>> I vaguely remember seeing a reference to a list of functions that
>> cause blocks of memory to be relocated.  [...]
>I'm not sure the list is that useful, especially when you start running
>INITs which patch otherwise memory-safe traps.
[...]
>Patch BlockMove and I'll kill you...

Patch *any* memory-safe trap in a memory-unsafe way and I'll kill you. But 
do you have any examples of INITs doing trap patches this way ?

Matthias

-- 
Matthias Neeracher                                   mneerach@iiic.ethz.ch
   "These days, though, you have to be pretty technical before you can 
    even aspire to crudeness." -- William Gibson, _Johnny Mnemonic_