Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!blekul11!GHGAPAR
From: GHGAPAR@BLEKUL11.BITNET (Tyberghein Jorrit)
Newsgroups: comp.sys.amiga.tech
Subject: Crash trapping
Message-ID: <15Mar1990150014125@BLEKUL11.BITNET>
Date: 15 Mar 90 14:59:09 GMT
Reply-To: GHGAPAR@BLEKUL11.BITNET
Organization: K.U.Leuven, Leuven (Belgium)
Lines: 14
Disclaimer: Author bears full responsibility for contents of this article

I'm writing a program to monitor system performance (something like
Xoper, only better I hope :-) I want to trap crashes. I already trap
the simply hardware crashes (crashes which result in a 'Task held'
rather than a 'GURU'). These were very easy to trap. Just point
the exception vectors to my code. The problem is that I want to trap
guru's (for example a 81000009 or 'free twice'). These crashes do
not result in a trap to one of the hardware exception vectors.
I think they use the exec function 'Alert'. I have tried to SetFunction
the Alert function but it still didn't work (the guru's keep coming).
Maybe I did something wrong, but I'd like your comments about this.
Am I doing this in the right manner or should I do it in another way.
I know it is possible because GOMF does trap real guru's.

                                 Tyberghein Jorrit