M/F 2:30-3:20 |
CS 1130: Transition to OO Programming Spring 2016 |
Main
About: Overview Announcements Staff Consultants Calendar Materials: Texts DrJava Terminology Lectures: In-Class Web-Based VideoNote Assessment: Grading Assignments Labs Resources: CMS Piazza (link) Piazza (about) Java API Style Guide Academic Integrity |
DebuggingIntroductionTesting is the process of running the program against test cases to try to uncover errors. Debugging is the process of looking for the cause of an uncovered error and then fixing it —once the cause has been found. Often the cause is far removed from the place at which the error manifests itself. Some people hate debugging, seeing it as a long, arduous, and frustrating task, like looking for a needle in a haystack. Others enjoy it, seeing it as a problem solving activity that requires the skill of a detective, who looks for evidence and sifts through it, trying to find out who committed a crime. There are two basic methods for tracking down a bug:
In this course, we concentrate on method (2), inserting print statements.
The next item asks you to watch a few lectures on the CD ProgramLive.
These lectures will step through the process of debugging a program.
Some part of the program calls a function Debugging maximsProgramLive, as well as the text Gries/Gries, present four maxims that help in tracking down bugs. Because they are important, we state them once more here:
|