Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!voder!apple!dgold
From: dgold@apple.UUCP
Newsgroups: comp.sys.mac
Subject: Re: MacWrite 4.5 BOMB
Message-ID: <546@apple.UUCP>
Date: Mon, 23-Mar-87 12:53:01 EST
Article-I.D.: apple.546
Posted: Mon Mar 23 12:53:01 1987
Date-Received: Wed, 25-Mar-87 04:36:56 EST
References: <121@osupyr.UUCP>
Reply-To: dgold@apple.UUCP (David Goldsmith)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 24

In article <121@osupyr.UUCP> pgn@.UUCP (Paul G. Nevai) writes:
>Do this: install MacsBug or something equivalent. Run MacWrite 4.5. Hit the
>interrupt switch. Then try to resume or go to the Finder. I can't. Can you?
>Do this: make a simple FKey doing nothing but ExitToShell. Use it on
>MacWrite 4.5 (or Excel). BOMBBBBB!. Why?
I've never had any problem entering Macsbug in either of these programs and
the continuing.  Perhaps you have a bad version of Macsbug.
As far as not being able to ExitToShell, it's possible that MacWrite patches
some traps (I know Excel does).  If they do not patch out ExitToShell in order
to clean up their patches if the program exits abnormally, then you will
return to the Finder with those patches installed.  Since they point into the
middle of the now-reinitialized application heap, the first time the Finder
calls one of those traps it will bomb.


-- 
David Goldsmith
Apple Computer, Inc.
MacApp Group

AppleLink: GOLDSMITH1
UUCP:  {nsc,dual,sun,voder,ucbvax!mtxinu}!apple!dgold
CSNET: dgold@apple.CSNET, dgold%apple@CSNET-RELAY
BIX: dgoldsmith