Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Debugging
Indu
Sharma
HOD(CSE)
CPTC,
Rajsamand
Introduction
 Debugging occurs as a consequence of
successful testing. That is, when a test
case uncovers an error, debug...
Debugging Process
Test
Cases
Execution
Of cases
Results
Debugging
Additional
test
Suspected
causes
Regression
test
Correct...
Debugging Process
 The debugging process begins with the execution
of a test case.
 Results are assessed and a lack of
c...
Debugging Approaches
 In general, there are three
categories for debugging
approaches:
1. Brute Force
2. Backtracking
3. ...
Brute Force
 Take memory dumps, invoke run time
traces, program is loaded with PRINT
statements.
 We hope that in the ma...
Backtracking
 Can be used successful in small programs.
 Beginning at the site where a symptom has
been uncovered the so...
Cause Elimination
 Introduces the concept of binary
partitioning.
 Uses binary partitioning to reduce the
number of loca...
Upcoming SlideShare
Loading in …5
×
Upcoming SlideShare
Debugging Approaches
Next
Download to read offline and view in fullscreen.

2

Share

Download to read offline

Debugging

Download to read offline

Debugging in SE

Related Books

Free with a 30 day trial from Scribd

See all

Debugging

  1. 1. Debugging Indu Sharma HOD(CSE) CPTC, Rajsamand
  2. 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. 3. Debugging Process Test Cases Execution Of cases Results Debugging Additional test Suspected causes Regression test Corrections Identified causes
  4. 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. 5. Debugging Approaches  In general, there are three categories for debugging approaches: 1. Brute Force 2. Backtracking 3. Cause Elimination
  6. 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. 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. 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.
  • MaNoKhanYusufZai

    Mar. 15, 2021
  • jyoshnasiddu

    Nov. 14, 2018

Debugging in SE

Views

Total views

7,976

On Slideshare

0

From embeds

0

Number of embeds

7

Actions

Downloads

235

Shares

0

Comments

0

Likes

2

×