Skip to main content
USENIX
  • Conferences
  • Students
Sign in
  • Overview
  • Workshop Organizers
  • Workshop Program
  • Sponsorship
  • Instructions for Participants
  • Call for Papers
  • Past Workshops

sponsors

Bronze Sponsor
Bronze Sponsor
Bronze Sponsor

connect with us


  •  Twitter
  •  Facebook
  •  LinkedIn
  •  Google+
  •  YouTube

twitter

Tweets by @usenix

usenix conference policies

  • Event Code of Conduct
  • Conference Network Policy
  • Statement on Environmental Responsibility Policy

You are here

Home » Failure Sketches: A Better Way to Debug
Tweet

connect with us

Failure Sketches: A Better Way to Debug

Monday, May 18, 2015 - 11:30am-12:00pm
Authors: 

Baris Kasikci, École Polytechnique Fédérale de Lausanne (EPFL); Cristiano Pereira and Gilles Pokam, Intel Corporation; Benjamin Schubert, École Polytechnique Fédérale de Lausanne (EPFL); Madanlal Musuvathi, Microsoft Research; George Candea, École Polytechnique Fédérale de Lausanne (EPFL)

Abstract: 

One of the main reasons debugging is hard and time consuming is that existing debugging tools do not provide an explanation for the root causes of failures. Additionally, existing techniques either rely on expensive runtime recording or assume existence of a given program input that reliably reproduces the failure, which makes them hard to apply in production scenarios. Consequently, developers spend precious time chasing elusive bugs, resulting in productivity loss.

We propose a new debugging technique, called failure sketching, that provides the developer with a high-level explanation for the root cause of a failure. A failure sketch achieves this goal because: 1) it only contains program statements that cause a failure; 2) it shows which program properties differ between failing and successful executions. We argue that failure sketches can be built by combining in-house static analysis and crowdsourced dynamic analysis. For building a failure sketch, we do not assume that developers can reproduce the failure. We show preliminary evidence that failure sketches can significantly improve programmer productivity.

Baris Kasikci, École Polytechnique Fédérale de Lausanne (EPFL)

Cristiano Pereira, Intel Corporation

Gilles Pokam, Intel Corporation

Benjamin Schubert, École Polytechnique Fédérale de Lausanne (EPFL)

Malandal Musuvathi, Microsoft Research

George Candea, École Polytechnique Fédérale de Lausanne (EPFL)

Open Access Media

USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.

BibTeX
@inproceedings {189889,
author = {Baris Kasikci and Cristiano Pereira and Gilles Pokam and Benjamin Schubert and Malandal Musuvathi and George Candea},
title = {Failure Sketches: A Better Way to Debug},
booktitle = {15th Workshop on Hot Topics in Operating Systems (HotOS XV)},
year = {2015},
address = {Kartause Ittingen, Switzerland},
url = {https://www.usenix.org/conference/hotos15/workshop-program/presentation/kasikci},
publisher = {USENIX Association},
month = may,
}
Download
Kasikci PDF
View the slides
  • Log in or    Register to post comments

Bronze Sponsors

© USENIX

  • Privacy Policy
  • Contact Us