Summary of Presentation for February 10, 1999

	We went through the material of pages 510 - 513 in the textbook
on debugging and repair.  The text combines both of these as separate 
processes while I treat them as different processes since an economic
decision might be made to not attempt repair once debugging has located
the source of the error that caused a particular fault.
	Debugging is both an art and a science.  There are some general
procedures that can be used which will almost always eventually succeed,
but the best debuggers depend on inspiration to break out of whichever
of those procedures they are using.  Remember that while brute force
approaches often work for small amounts of code, more thoughtful
approaches are necessary for larger segments of code.
	We will use the sample program of February 10th as an extended 
example during the next few periods as we attempt to test, debug and
repair at least a couple of functions in that program.