Why Programs Fail: A Guide to Systematic Debugging

Front Cover
Elsevier, Jul 22, 2009 - Computers - 544 pages

Why Programs Fail: A Guide to Systematic Debugging is proof that debugging has graduated from a black art to a systematic discipline. It demystifies one of the toughest aspects of software programming, showing clearly how to discover what caused software failures, and fix them with minimal muss and fuss.

The fully updated second edition includes 100+ pages of new material, including new chapters on Verifying Code, Predicting Erors, and Preventing Errors. Cutting-edge tools such as FindBUGS and AGITAR are explained, techniques from integrated environments like Jazz.net are highlighted, and all-new demos with ESC/Java and Spec#, Eclipse and Mozilla are included.

This complete and pragmatic overview of debugging is authored by Andreas Zeller, the talented researcher who developed the GNU Data Display Debugger(DDD), a tool that over 250,000 professionals use to visualize the data structures of programs while they are running. Unlike other books on debugging, Zeller's text is product agnostic, appropriate for all programming languages and skill levels.

The book explains best practices ranging from systematically tracking error reports, to observing symptoms, reproducing errors, and correcting defects. It covers a wide range of tools and techniques from hands-on observation to fully automated diagnoses, and also explores the author's innovative techniques for isolating minimal input to reproduce an error and for tracking cause and effect through a program. It even includes instructions on how to create automated debugging tools.

The text includes exercises and extensive references for further study, and a companion website with source code for all examples and additional debugging resources is available.

  • The new edition of this award-winning productivity-booster is for any developer who has ever been frustrated by elusive bugs
  • Brand new chapters demonstrate cutting-edge debugging techniques and tools, enabling readers to put the latest time-saving developments to work for them
  • Learn by doing. New exercises and detailed examples focus on emerging tools, languages and environments, including AGITAR, FindBUGS, Python and Eclipse
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Contents

Chapter 1 How Failures Come to Be
1
Chapter 2 Tracking Problems
25
Chapter 3 Making Programs Fail
49
Chapter 4 Reproducing Problems
75
Chapter 5 Simplifying Problems
105
Chapter 6 Scientific Debugging
129
Chapter 7 Deducing Errors
147
Chapter 8 Observing Facts
175
Chapter 12 Causes and Effects
271
Chapter 13 Isolating Failure Causes
283
Chapter 14 Isolating CauseEffect Chains
305
Chapter 15 Fixing the Defect
329
Chapter 16 Learning from Mistakes
343
Appendix Formal Definitions
363
Glossary
377
Bibliography
381

Chapter 9 Tracking Origins
211
Chapter 10 Asserting Expectations
223
Chapter 11 Detecting Anomalies
253

Other editions - View all

Common terms and phrases

About the author (2009)

Andreas Zeller is a full professor for Software Engineering at Saarland University in Saarbruecken, Germany. His research concerns the analysis of large software systems and their development process; his students are funded by companies like Google, Microsoft, or SAP. In 2010, Zeller was inducted as Fellow of the ACM for his contributions to automated debugging and mining software archives. In 2011, he received an ERC Advanced Grant, Europe's highest and most prestigious individual research grant, for work on specification mining and test case generation. His book "Why programs fail", the "standard reference on debugging", obtained the 2006 Software Development Jolt Productivity Award.

Bibliographic information