Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!pasteur!ucbvax!DHHDESY3.BITNET!F1FPAW
From: F1FPAW@DHHDESY3.BITNET (Jerzy Michal Pawlak)
Newsgroups: comp.sys.atari.st
Subject: Re: Trapping Errors
Message-ID: <8802011242.AA20489@ucbvax.Berkeley.EDU>
Date: 1 Feb 88 12:42:53 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15
X-Unparsable-Date: MON,  1 FEB 88 12:27:46 MEZ


>Can anyone tell me if there's a good way to trap the kinds of errors
>that usually result in bombs?

The bombing routine is entered via the exception vectors (some of them
are: bus error, address error, illegal instruction ...). Just change
the vectors to point to your debugger.

>Is there a better substitute for MUSHROOM, or
>documentation on where to find the crash data and how to interpret it?

Yes, I use MONST (very good!). By the way: MONST does trap bombs in
a correct way.

                 Michal Pawlak (I'm not an expert!)