At 1:07 AM -0400 on 4/30/02, Robert Covington wrote:

>  >Get HexEdit, there are OS 9 and OS X versions available.  It can
>>search and browse data and resource forks.  It also comes with full
>>source code and projects for Project Builder, CodeWarrior and MPW.
>>Oh, and it's free and the source is covered under the Mozilla Public
>>license.
>
>I would prefer something more automatic...didn't know if RP or Jay or
>others could whip up something interesting.

HexEdit is an application, you don't have to build the source, sorry 
if I was unclear.  It isn't as automatic as NDE since you have to use 
it on specific files.

>  >Can you do a stack chain (SC7 or SC6 IIRC) or does MacsBug
>>show a label where the crash is, like the name of a fragment or
>>function?
>
>Just says Illegal instruction at _A008 I think. The app name always varies.

There is a 68k trap at 0xA008, it's for PBCreateSync  I don't know if 
it helps or not.  What kind of build is this, PPC, 68k, Carbon, etc.?

I'm sure there are MacsBug experts here that can give more info but 
try either SC7 or SC6 and see what functions led to the crash.  They 
display a list of return addresses.  It can help figure out what 
functions were called before the crash.  Of course, if you can't save 
it to a log file it might not help much

It might not help much but StdLog expands to these commands:

dv v;stat;wh;td;ip;hz;hc all;sys;ht;pm;ht;app;ht;file 
0;vol;drive;drvr -v;rd -s;sc6;sc7 sp 1k;dm sp 80;dm 0 20

Each command delimited by a ;

Since the filesystem is busy you might try seeing which files are 
open.  Have you also done heap checks after the crash?

-- 
Heather Donahue