#: 18596 S12/OS9/68000 (OSK)
    25-Aug-93  08:24:04
Sb: #18182-68k bus errors
Fm: Kim Kempf 71161,3221
To: Chris Hann (Mass UK) 100064,1431

When I have a problem with an unknown #102 error I use the following technique:

load up the program module and the .stb.  Use the old trusty 'debug' program:
'debug prog'.  At the prompt say: 'x-1'.  This will run the program at full
speed (not trace mode).  If the program causes an exception, the debugger will
catch it and stop close to where the exception happened.  You have to look a
few instructions back to find the offending one, but at least you have the
register display to give a clue to the bad address.  Since the program is not a
system-state process, there is no stack frame to look at, but you do know what
the caused the exception (from the error code 102, 103, etc.)

You can also use this technique to set a breakpoint and run at full speed.  The
kernel will remove the breakpoint from the object code when the debugging task
is task switched.  This is useful for debugging code that another process is
running.