Skip to main content
SpringerLink
Log in

Cooperative Bug Isolation

Winning Thesis of the 2005 ACM Doctoral Dissertation Competition

  • Book
  • © 2007

Overview

Authors:
  1. Ben Liblit
    View author publications

    You can also search for this author in PubMed   Google Scholar

Part of the book series: Lecture Notes in Computer Science (LNCS, volume 4440)

Part of the book sub series: Programming and Software Engineering (LNPSE)

  • 1884 Accesses

This is a preview of subscription content, log in via an institution to check access.

Access this book

Log in via an institution
eBook USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (6 chapters)

  1. Front Matter

    Download chapter PDF

  2. Introduction

    • Ben Liblit
    Pages 1-6

  3. Instrumentation Framework

    • Ben Liblit
    Pages 7-38

  4. Practical Considerations

    • Ben Liblit
    Pages 39-54

  5. Techniques for Statistical Debugging

    • Ben Liblit
    Pages 55-88

  6. Related Work

    • Ben Liblit
    Pages 89-93

  7. Conclusion

    • Ben Liblit
    Pages 95-96

  8. Back Matter

    Download chapter PDF
Back to top

Keywords

About this book

Efforts to understand and predict the behavior of software date back to the earliest days of computer programming,over half a century ago. In the intervening decades, the need for effective methods of understanding software has only increased; so- ware has spread to become the underpinning of much of modern society, and the potentially disastrous consequences of broken or poorly understood software have become all too apparent. Ben Liblit’s work reconsiders two common assumptions about how we should analyze software and it arrives at some striking new results. Inprinciple,understandingsoftware is not such a hardproblem. Certainlya c- puter scientist studying programs appears to be in a much stronger position than, say, a biologist trying to understand a living organism or an economist trying to understand the behavior of markets, because the biologist and the economist must rely on indirect observation of the basic processes they wish to understand. A c- puterscientist, however,starts with a complete,precise descriptionof the behaviorof software—the program itself! Of course, the story turns out not to be so straightf- ward, because despite having a perfect description, programs are suf ciently c- plex that it is usually dif cult or even impossible to answer many simple questions about them.

Bibliographic Information

Publish with us

Policies and ethics

Back to top

Search

Navigation