• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations

DMCA

Fault Localization with Nearest Neighbor Queries (2003)

Cached

  • Download as a PDF

Download Links

  • [www.cs.brown.edu]
  • [www.cs.brown.edu]
  • [www.cs.brown.edu]
  • [cs.brown.edu]
  • [cs.brown.edu]
  • [www.cs.purdue.edu]
  • [www.cs.purdue.edu]
  • [cs.brown.edu]
  • [www.cs.purdue.edu]
  • [cs.brown.edu]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Manos Renieris , Steven P. Reiss
Citations:233 - 2 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@MISC{Renieris03faultlocalization,
    author = {Manos Renieris and Steven P. Reiss},
    title = {Fault Localization with Nearest Neighbor Queries},
    year = {2003}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

We present a method for performing fault localization using similar program spectra. Our method assumes the existence of a faulty run and a larger number of correct runs. It then selects according to a distance criterion the correct run that most resembles the faulty run, compares the spectra corresponding to these two runs, and produces a report of "suspicious" parts of the program. Our method is widely applicable because it does not require any knowledge of the program input and no more information from the user than a classification of the runs as either "correct" or "faulty". To experimentally validate the viability of the method, we implemented it in a tool, WHITHER using basic block profiling spectra. We experimented with two different similarity measures and the Siemens suite of 132 programs with injected bugs. To measure the success of the tool, we developed a generic method for establishing the quality of a report. The method is based on the way an "ideal user" would navigate the program using the report to save effort during debugging. The best results we obtained were, on average, above 50%, meaning that our ideal user would avoid looking at half of the program.

Keyphrases

fault localization    nearest neighbor query    ideal user    correct run    faulty run    injected bug    generic method    basic block    spectrum corresponding    distance criterion    similar program spectrum    program input    different similarity measure    siemens suite    suspicious part   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University