Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!caip!cbmvax!randy
From: randy@cbmvax.cbm.UUCP (Randy Weiner)
Newsgroups: net.micro.amiga
Subject: Re: How to prevent system death from errors in user code?
Message-ID: <307@cbmvax.cbmvax.cbm.UUCP>
Date: Fri, 30-May-86 13:00:17 EDT
Article-I.D.: cbmvax.307
Posted: Fri May 30 13:00:17 1986
Date-Received: Sat, 31-May-86 07:24:57 EDT
References: <758@jade.BERKELEY.EDU>
Reply-To: randy@cbmvax.UUCP (Randy Weiner)
Organization: Commodore Technology, West Chester, PA
Lines: 26

In article <758@jade.BERKELEY.EDU> mkent@violet.berkeley.edu.UUCP () writes:
>
>   I've been doing some development on the Amiga with the Lattice C
>compiler ...any runtime error in my C programs...crashes the
>entire system.
>... This is usually accompanied by some kute and klever guru 
>meditation number, about which I've been unable to find any explanation...

	The information you seek may be found in the include file,
exec/alerts.h. Here is where the system DEFINEs are located for
most of the possible errors. This is especially helpful in Version 3.02
since the comments should still be part of the disk file.

	In brief, the number to the left of the '.' represents
an error number, and the number to the right is the address of the
task/process that has failed. User programs are typically loaded
at address $97D2 (or thereabouts). Look familiar?


-- 
     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
Randy Weiner -- Commodore Business Machines <<Amiga Technical Support>>
		uucp: {ihnp4|seismo|caip}!cbmvax!randy
		arpa: cbmvax!randy@seismo
		(or)  randy@cbmvax.UUCP@{seismo | harvard}
		TEL:  215-431-9180