Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!x194 From: x194@cs.utexas.edu (Jonathan Abbey) Newsgroups: comp.sys.amiga.tech Subject: Re: Help --> How to prevent the visit from the dreaded guru Summary: Use a debugger Message-ID: <133@atacama.cs.utexas.edu> Date: 6 Jan 91 02:37:24 GMT References: <611@caslon.cs.arizona.edu> <1991Jan4.203339.8800@maytag.waterloo.edu> Organization: U. Texas CS Dept., Austin, Texas Lines: 19 The best thing to do to guard yourself from GURU's during software development is to use a debugger to run your code. There is one available on a relatively recent fred fish disk which will suffice to debug software that doesn't take over the display in some fashion. Even then you could patch it to open aux: instead of a con: window, and hook it up to a terminal. In either case, you can have the debugger run the code in 68000 trace mode so that any guru inspiring phenomena will just return to the debugger rather than bring the system down. This won't catch all possible errors, though.. you can still feed a system function bad information, as well as overwrite system structures. Has anyone written a debugger that will try to watch out for your code a bit? That is, that will monitor the PC during a trace and let you specify various behaviors if your task goes outside of a certain set of memory regions? ------------------------------------------------------------------------------- Jonathan Abbey The University of Texas at Austin x194@cs.utexas.edu Computer Science-Math?-Psychology? --