Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!ll-xn!ames!lll-tis!oodis01!uplherc!sp7040!obie!wes
From: wes@obie.UUCP
Newsgroups: comp.sys.atari.st
Subject: Re: Bomb list
Summary: Catching bombs?
Message-ID: <228@obie.UUCP>
Date: 11 May 88 08:01:01 GMT
References: <2905@saturn.ucsc.edu> <1773@netmbx.UUCP> <477@philmds.UUCP> <12463@tut.cis.ohio-state.edu>
Organization: Great Salt Lake Yacht Club, north branch
Lines: 28
Posted: Wed May 11 04:01:01 1988

In article <12463@tut.cis.ohio-state.edu>, weaver@tut.cis.ohio-state.edu (Andrew Weaver) writes:
> Is there a way to intercept the 'bombs' that come onto
> the screen with some sort of dialog like on the Mac [...]
> or on the Amiga: [...]

Sure.  The bombs are drawn on the screen by the default handler for
the following processor exceptions:

	2  Bus error
	3  Address error
	4  Illegal instruction
	5  Zero divide
	6  CHK instruction
	7  TRAPV instruction
	8  Priviledge violation
	9  Trace trap
	A  Line A emulator
	B  Line F emulator
	C  Reserved
	D  Reserved
	E  Reserved

You could simply write a Ptermres program that points the vectors for
these exceptions (except Line A and Line F) to your code, and have the
code pop up an alert with some useful information.  The bombs tell you
which exception you got, however, and the information about the
processor's context at the time of the crash is stored in a buffer in
low memory so you can access after a crash, even after a warm boot.