Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!ml27192
From: ml27192@uxa.cso.uiuc.edu (Mark  Lanett)
Newsgroups: comp.sys.mac.programmer
Subject: Learning MacsBug
Summary: How/Where do you learn to use MacsBug to find out source of crashes?
Keywords: MacsBug, Debugging
Message-ID: <1990Dec18.181638.23301@ux1.cso.uiuc.edu>
Date: 18 Dec 90 18:16:38 GMT
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 14

Now that I'm using system 6.0.7 and ~20 inits, I'm being dumped into MacsBug
an awful lot. I'd like to be able to use it to figure out what the problems are:
they're never obvious enough for me to be able to finger one init, and I don't
have the time to restart the machine and run MPW for each combination to figure
out what it is. Of course, only knowing 'rs', 'es', and 'ea' that is basically
what I'm doing now...

So, where does one find out about heaps and such? Also, is there any way to
forcefully recover from a crash (forcefully recover?) I hate being under MF
and having one little program's crash force me to reboot. Isn't one ability
of being under MF that of being able to just dump that program and continue
elsewhere? I mean when 'sm 0 a9f4; g 0' doesn't work.

Mark "two-minute reboot time" Lanett