Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!seismo!lll-crg!styx!nike!cad!ucbvax!jade!violet.berkeley.edu!mkent
From: mkent@violet.berkeley.edu.berkeley.edu (/violet_d/mkent)
Newsgroups: net.micro.amiga
Subject: How to prevent system death from errors in user code?
Message-ID: <758@jade.BERKELEY.EDU>
Date: Thu, 29-May-86 01:18:09 EDT
Article-I.D.: jade.758
Posted: Thu May 29 01:18:09 1986
Date-Received: Sat, 31-May-86 06:08:59 EDT
Sender: usenet@jade.BERKELEY.EDU
Reply-To: mkent@violet.berkeley.edu.UUCP ()
Organization: University of California, Berkeley
Lines: 21


   I've been doing some development on the Amiga with the Lattice C
compiler (in fact I have the old version, 3.02 I believe).  I'm having
the general problem that any runtime error in my C programs, even
something like passing a routine an int instead of a float, crashes the
entire system (so I have to reboot and reload the entire system, and of
course all context of the error is lost).  This is usually accompanied
by some kute and klever guru meditation number, about which I've been
unable to find any explanation in my (also version 1) ROM kernal
manual.  Of course, this kind of behavior renders debugging extremely
painful and slow.
   The amiga is my first experience with a microcomputer; I do most of
my work on lisp machines and vaxen.  I want to beleive there's some
simple thing I'm failing to do which will enable the system to give
some useful information and, most importantly, not to just roll over
and drop dead when it encounters an error in user code.  (I'd like not
to believe I've spent $2000 on some kind of TOY!)  Can someone tell me 
what the actual situation is about this?
			Thanks,
			Marty Kent
		MKent%ucbviolet@berkeley.edu