Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!ncar!ames!pasteur!zooey.Berkeley.EDU!c162-br From: c162-br@zooey.Berkeley.EDU (Warner Young) Newsgroups: comp.sys.atari.st Subject: Re: Bomb list Message-ID: <3215@pasteur.Berkeley.Edu> Date: 9 May 88 18:37:24 GMT References: <2905@saturn.ucsc.edu> <1773@netmbx.UUCP> <477@philmds.UUCP> <12463@tut.cis.ohio-state.edu> <424@hvrunix.UUCP> Sender: news@pasteur.Berkeley.Edu Reply-To: c162-br@zooey.Berkeley.EDU.UUCP (Warner Young) Organization: University of California, Berkeley Lines: 29 Keywords: Compute bombs exception traps In article <12463@tut.cis.ohio-state.edu>, weaver@tut.cis.ohio-state.edu (Andrew Weaver) writes: > Here is a question I don't think I have ever heard hashed around > on here before. Is there a way to intercept the 'bombs' that come onto > the screen with some sort of dialog like on the Mac: "Sorry, > a system error has occureed [Restart|Resume]" or on the Amiga: "System > Error: Guru Meditiation xxx:xxxxxxx [Continue]" so that one can better > diagnose problems with one's own (or someone else's) program? It seems > to me that having a number of non-descript cherry bombs (or mushroom clouds, > which I am told appeared on earlier STs) is not a very good way of represent- > ing an error, but I guess that's just me. > Andrew Weaver weaver@tut.cis.ohio-state.edu As a matter of fact, it is possible to "trap" the exception vectors to run your own routines. Compute!'s book on C Programming on the ST has a program that does just this, called Bombsite (or something like that). I have no permission to post the program here, and it's written in a format that would be rather unwieldy to post, but I suggest you check out this book; it's quite good. \ /arner - Writer of the dreaded Safety Seal Reviews \ / / - Owner of the vaporware group Safety Seal Software \/ \_/oung | - Disclaimer: I'm not associated with any of the companies \_| above, in any way except (possibly) as a customer.