Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!pasteur!ucbvax!STONY-BROOK.SCRC.Symbolics.COM!jrd
From: jrd@STONY-BROOK.SCRC.Symbolics.COM (John R. Dunning)
Newsgroups: comp.sys.atari.st
Subject: Trapping errors
Message-ID: <19880126193720.1.JRD@GRACKLE.SCRC.Symbolics.COM>
Date: 26 Jan 88 19:37:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

Can anyone tell me if there's a good way to trap the kinds of errors
that usually result in bombs?  I'm contemplating porting a debugger to
the ST, but a fundamental piece of functionality is the ability to use
my own trap vectors, or at least the get TOS to give control back to me
with a pointer to the crash data.  I would expect there to be some sort
of OS call for this, but haven't seen it.

Related question:  Does MUSHROOM.PRG work?  Whenever I run it it appears
to just dump a piece of the system stack, with no indication of the user
PC or failing instruction etc.  It then crashes itself with an
alignment error.  Is there a better substitute for MUSHROOM, or
documentation on where to find the crash data and how to interpret it?

Thanks.