Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!uwvax!umn-d-ub!umn-cs!dayton!joe
From: joe@dayton.UUCP (Joseph P. Larson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Who did it!
Keywords: Crash, GURU, Alert
Message-ID: <5316@dayton.UUCP>
Date: 16 Jun 88 18:09:19 GMT
References: <180@snll-arpagw.UUCP>
Reply-To: joe@dayton.UUCP (Joseph P. Larson)
Organization: Dayton-Hudson Dept. Store Co.
Lines: 22

paolucci@snll-arpagw.UUCP (Sam Paolucci) writes:
>.....I don't know if
>this is doable, since I haven't given it a lot of thought, but what we
>need is a utility that sits in the background and points a finger (via
>a requester) at the software that was responsible for the crash.

One problem is the following scenario:

	program A is happily purring along.
	program B comes along with an invalid pointer and stomps on
		program A's data or even code.
	program A causes a crash.

Who's at fault?  How is your little background program going to know that
it was program B who caused the crash when it was program A that was running
when the crash occured?

Good luck. -J
-- 
UUCP: rutgers!dayton!joe                Dayton Hudson Department Store Company
ATT : (612) 375-3537                    Joe Larson/MIS 1060
(standard disclaimer...)                700 on the Mall      Mpls, Mn. 55402