🚀 go-pugleaf

in article <6530@cup.portal.com>, Doug_B_Erdely@cup.portal.com says:
> XPortal-User-Id: 1.1001.2946

> Gomf 2.2 does almost this! It will tell you when something not nice is done
> to the system! I use this program, and it makes it very easy to figure out
> what program did the no no.

Sometimes.  But imagine this.  Program A starts up and runs very nicely.  
Program B starts up and happens to write something through an uninitialized
pointer that just happens to point to something that program A is using.  
At some point, program A gets back to this corrupt instruction or data, and
vomits.  Gomf 2.2 (haven't used it myself) may be extremely clever, and 
catch the program in it's death throes.  But while it's catching the program
that barfed, that's not the program that caused the barf.  I do suspect,
though, that such error trapping progams like Gomf would be useful to the
developer working in a solid evironment with only the program under
development capable of thrashing the system.

>          - Doug -
-- 
Dave Haynie  "The 32 Bit Guy"     Commodore-Amiga  "The Crew That Never Rests"
   {ihnp4|uunet|rutgers}!cbmvax!daveh      PLINK: D-DAVE H     BIX: hazy
		"I can't relax, 'cause I'm a Boinger!"