The document discusses debugging processes. It begins by defining debugging as finding and correcting software errors uncovered during testing. The debugging process involves executing test cases, assessing results for discrepancies between expected and actual performance, and attempting to find the cause through iterative testing and corrections. There are generally three debugging approaches: brute force using extensive logging, backtracking by tracing code backwards from symptoms, and cause elimination using binary partitioning to isolate potential error causes.

1. Debugging
Indu
Sharma
HOD(CSE)
CPTC,
Rajsamand

2. Introduction
 Debugging occurs as a consequence of
successful testing. That is, when a test
case uncovers an error, debugging is
the process that results in the removal
of the error.
 Debugging has the objective: to find
and correct the cause of a software
error.

3. Debugging Process
Test
Cases
Execution
Of cases
Results
Debugging
Additional
test
Suspected
causes
Regression
test
Corrections
Identified
causes

4. Debugging Process
 The debugging process begins with the execution
of a test case.
 Results are assessed and a lack of
correspondence between expected and actual
performance is encountered.
 The debugging process will always have one of two
outcomes:
1. The cause will be found and corrected, or
2. The cause will not be found.
 In the latter case, the person performing debugging
may suspect a cause, design a test case to help
validate that suspicion, and work toward error
correction in an iterative fashion.

5. Debugging Approaches
 In general, there are three
categories for debugging
approaches:
1. Brute Force
2. Backtracking
3. Cause Elimination

6. Brute Force
 Take memory dumps, invoke run time
traces, program is loaded with PRINT
statements.
 We hope that in the mass of information
that is produced we will find a clue that can
lead us to the cause of an error.
 Least efficient and quite common.
 More frequently leads to wasted effort and
time.

7. Backtracking
 Can be used successful in small programs.
 Beginning at the site where a symptom has
been uncovered the source code is traced
backward (manually) until the site of the
cause is found.
 Disadvantage: as the number of source line
increases, the number of potential paths
may become unmanageably large.

8. Cause Elimination
 Introduces the concept of binary
partitioning.
 Uses binary partitioning to reduce the
number of locations potential where
errors can exist
 Isolate potential causes, devise
cause hypotheses tests to isolate bug.