Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!tness7!tness1!nuchat!uunet!pyrdc!netxcom!ewiles
From: ewiles@netxcom.UUCP (Edwin Wiles)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Who did it!
Keywords: Crash, GURU, Alert
Message-ID: <864@netxcom.UUCP>
Date: 17 Jun 88 16:26:11 GMT
References: <180@snll-arpagw.UUCP> <4022@cbmvax.UUCP> <183@snll-arpagw.UUCP>
Reply-To: ewiles@netxcom.UUCP (Edwin Wiles)
Organization: NetExpress Communications, Inc., Vienna, VA
Lines: 23

In <183@snll-arpagw.UUCP> paolucci@snll-arpagw.UUCP (Sam Paolucci) writes:
> In <4022@cbmvax.UUCP> carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) writes:
> > In <180@snll-arpagw.UUCP> paolucci@snll-arpagw.UUCP (Sam Paolucci) writes:
> > >...a utility that sits in the background and points a finger (via
> > >a requester) at the software that was responsible for the crash...
> >
> >...A badly written program can trash some other program's memory...
> >...No way to tell which task DID the trashing...
>
>...I am not suggesting that just because this happens once, that the
>particular task pointed to should be immediately blamed...

The problem is that many users will simply blame it right away, and won't
bother to check it out under different configurations.  It's not technically
impossible, but it *is* socially impossible.  Too many users *would*
immediately blame the one pointed at, without thinking about the fact that
someone else is at fault.

-- 
...!hadron\   "Who?... Me?... WHAT opinions?!?" | Edwin Wiles
  ...!sundc\   Schedule: (n.) An ever changing	| NetExpress Comm., Inc.
   ...!pyrdc\			  nightmare.	| 1953 Gallows Rd. Suite 300
    ...!uunet!netxcom!ewiles			| Vienna, VA 22180