Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!littlei!ogcvax!afoster From: afoster@ogcvax.UUCP (Allan Foster) Newsgroups: comp.sys.mac Subject: Re: What does access memory manager' mean? Message-ID: <1446@ogcvax.UUCP> Date: Sat, 10-Oct-87 18:21:06 EDT Article-I.D.: ogcvax.1446 Posted: Sat Oct 10 18:21:06 1987 Date-Received: Wed, 14-Oct-87 04:29:08 EDT References: Reply-To: afoster@ogcvax.UUCP (Allan Foster) Organization: Oregon Graduate Center, Beaverton, OR Lines: 29 In article jmm@thoth14.berkeley.edu () writes: >In IM, it says that you can't use any >routines that access the memory manager >directly or indirectly from within >things such as VBL tasks, system tasks, etc. >Does this mean that any system call that >can cause heap scrambles is disallowed? > >James Moore >ucbvax!leggatt!jmm This means exactly what it says. YOU CANNOT USE ANY ROUTINE THAT USE THE MEMORY MANAGER!!!! The reason for this is that the interupt that started your routine running could have interupted the memory manager in its work. It may be moving the heap around, so the only thing that you can rely on is that any locked handles and pointers will be valid. You cannot even call anything that gets or disposes allocated memory. The state of the momory manager is totally unknown!! Regards Allan Foster. Hey, You can't do that, You're DEAD --The living Daylights Allan Foster UUCP : tektronix!ogcvax!afoster GEnie : A.FOSTER AppleLink : UG0035 USPS : 1340 SE 89 Portland OR 97216 Voice : (503) 257-0573 Voice : (503) 252-1351 CSNet : afoster@Oregon-Grad