dudek@ai.toronto.edu (Gregory Dudek) (03/17/90)
While doing development under multifinder (or even normally just doing stuff) it's not uncommon for an application to land me in MacsBug & for it to be too trashed to continue. In many cases I can't exit either, probably because the dead app. has patched exit-to-shell. Is there any way to force MultiFinder to make a context switch or to trash the offending partition? That way I can at least close down my other applications in an orderly manner. Isn't this pretty much what MF does when it says the application has "unexpectedly quit" (which it doesn't do when MacsBug is loaded). Greg Dudek
ml10+@andrew.cmu.edu (Michael A. Libes) (03/17/90)
> Is there any way to force MultiFinder to make a context switch or > to trash the offending partition? That way I can at least > close down my other applications in an orderly manner. To do a context switch in MacsBug under normal circumstances, do a trap break, "atb A88F" which is the OSDispatch (JugglerDispatch is a historic name) trap call. At location 0x910, you will find CurApName, the current application name. If you type "show 910 a" it'll display the current application name in the upper left of the screen. To do a context switch, keep typing "g <ret>" until the desired application is shown. To remove the trap break, type "atc" To get a trashed application to exit, try typing "es". This should produce the "unexpectedly quit" dialog box. If that doesn't work, I usually reboot the machine. - Luni