1 / 13

Delta Debugging - Demo

Delta Debugging - Demo . Presented by: Xia Cheng. Motivation. Automation is difficult fail analysis needs complete understanding of the program Automated debugging tools – Delta Debugging to resolve the problems. History.

kent
Télécharger la présentation

Delta Debugging - Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Delta Debugging - Demo Presented by: Xia Cheng

  2. Motivation • Automation is difficult • fail analysis needs complete understanding of the program • Automated debugging tools –Delta Debugging to resolve the problems

  3. History • In 2001, Andreas Zeller wrote an article “Automated Debugging: Are We Close?” • Zeller’s studies regarding the isolation of cause-effect chains from computer programs and the simplification of failure-inducing input • Eclipse’s interactivity with JUnit is an advantage of the platform

  4. Delta Debugging • automated debugging approach based on systematic testing • Find failure-inducing circumstances automatically— • Circumstances, such as the program input, changes to the program code, or program executions.

  5. DDInput • Failure-Inducing Input • Find out which part of the input causes your program to fail

  6. The goal of DDInput • to automatically minimize an input file until only the part relevant for a failure remains • with the DDInput plug-in, this huge file can automatically be minimized until only the failure-inducing statement remains. • To implement it by JUnit test case

  7. Functionality of DDInput • Run DDInput as soon as JUnit test fails • Determine, if the failing JUnit test opens a resource • If it opens a file, determine if the file is responsible for the failing of the test • If the file is responsible, minimize it by using DDCore • Show the process of the Delta Debugging algorithm and the results to the user

  8. Installation • Go to http://www.st.cs.uni-sb.de/eclipse/ • Click DDInput and download DDCore_DDInput.zip • Unzipped it into Eclipse folder

  9. Configuration • Start ECLIPSE. • Select Help→ Software Updates→ Find and Install... • Choose Search for new features to install and select Next. • Select The Eclipse Project Updates

  10. Configuration (Cont.) • Read the license and accept the terms (if you agree) and select Next. • Choose the ECLIPSE installation and select Finish. • The feature is not signed (yet), so likely we will get a warning. Select Install. • Restart the ECLIPSE workbench to complete the installation.

  11. Application Guide • Create Delta Debugging View • Click Eclipse main menu Window • Choose Show View->Other… • In Java folder, choose DeltaDebugging View • Delta Debugging View includes: • Isolate Failure-Inducing Input • Minimize Failure-Inducing Input

  12. Application Guide • File->New->JUnit Test Case • Name the file • Outline window shows the file name and all its method names

  13. Limitation • Add the possibility to abort the process • Increase the stability • Fix a probable memory hole

More Related