Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!decwrl!apple!dlyons
From: dlyons@Apple.COM (David A. Lyons)
Newsgroups: comp.sys.apple2
Subject: Re: Error Detective
Message-ID: <44111@apple.Apple.COM>
Date: 20 Aug 90 19:40:17 GMT
References: <1990Aug20.021901.28351@utstat.uucp>
Distribution: na
Organization: Apple Computer Inc, Cupertino, CA
Lines: 20

In article <1990Aug20.021901.28351@utstat.uucp> philip@utstat.uucp (Philip McDunnough) writes:
>[...]
>Is there a utility of sorts which will indicate an offending program? That
>is, is there a program available which associates errors with programs and
>vice versa?

No, probably not.  Sure, you could write something that tells you which
application or DA actually made the call to SysFailMgr, but that doesn't
tell you whose fault it was that the unrecoverable condition came about.

In general, somebody actually has to look at the code & see who's doing
what wrong.
-- 
David A. Lyons, Apple Computer, Inc.      |   DAL Systems
Apple II Developer Technical Support      |   P.O. Box 875
America Online: Dave Lyons                |   Cupertino, CA 95015-0875
GEnie: D.LYONS2 or DAVE.LYONS         CompuServe: 72177,3233
Internet/BITNET:  dlyons@apple.com    UUCP:  ...!ames!apple!dlyons
   
My opinions are my own, not Apple's.