LIMITED OFFER
Save 50% on book bundles
Immediately download your ebook while waiting for your print delivery. No promo code needed.
Why Programs Fail
A Guide to Systematic Debugging
- 2nd Edition - June 12, 2009
- Author: Andreas Zeller
- Language: English
- Paperback ISBN:9 7 8 - 0 - 1 2 - 3 7 4 5 1 5 - 6
- eBook ISBN:9 7 8 - 0 - 0 8 - 0 9 2 3 0 0 - 0
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 o… Read more
Purchase options
Institutional subscription on ScienceDirect
Request a sales quoteWhy 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
Computer programmers, software developers, analysts and testers
- Cover
- Title page
- Table of Contents
- Copyright
- Foreword
- Preface
- ACKNOWLEDGMENTS
- Chapter 1: How Failures Come to Be
- 1.1 MY PROGRAM DOES NOT WORK!
- 1.2 FROM DEFECTS TO FAILURES
- 1.3 LOST IN TIME AND SPACE
- 1.4 FROM FAILURES TO FIXES
- 1.5 AUTOMATED DEBUGGING TECHNIQUES
- 1.6 BUGS, FAULTS, OR DEFECTS?
- 1.7 CONCEPTS
- 1.8 TOOLS
- 1.9 FURTHER READING
- Chapter 2: Tracking Problems
- 2.1 OH! ALL THESE PROBLEMS
- 2.2 REPORTING PROBLEMS
- 2.3 MANAGING PROBLEMS
- 2.4 CLASSIFYING PROBLEMS
- 2.5 PROCESSING PROBLEMS
- 2.6 MANAGING PROBLEM TRACKING
- 2.7 REQUIREMENTS AS PROBLEMS
- 2.8 MANAGING DUPLICATES
- 2.9 RELATING PROBLEMS AND FIXES
- 2.10 RELATING PROBLEMS AND TESTS
- 2.11 CONCEPTS
- 2.12 TOOLS
- 2.13 FURTHER READING
- Chapter 3: Making Programs Fail
- 3.1 TESTING FOR DEBUGGING
- 3.2 CONTROLLING THE PROGRAM
- 3.3 TESTING AT THE PRESENTATION LAYER
- 3.4 TESTING AT THE FUNCTIONALITY LAYER
- 3.5 TESTING AT THE UNIT LAYER
- 3.6 ISOLATING UNITS
- 3.7 DESIGNING FOR DEBUGGING
- 3.8 PREVENTING UNKNOWN PROBLEMS
- 3.9 CONCEPTS
- 3.10 TOOLS
- 3.11 FURTHER READING
- Chapter 4: Reproducing Problems
- 4.1 THE FIRST TASK IN DEBUGGING
- 4.2 REPRODUCING THE PROBLEM ENVIRONMENT
- 4.3 REPRODUCING PROGRAM EXECUTION
- 4.4 REPRODUCING SYSTEM INTERACTION
- 4.5 FOCUSING ON UNITS
- 4.6 REPRODUCING CRASHES
- 4.7 CONCEPTS
- 4.8 TOOLS
- 4.9 FURTHER READING
- Chapter 5: Simplifying Problems
- 5.1 SIMPLIFYING THE PROBLEM
- 5.2 THE GECKO BUGATHON
- 5.3 MANUAL SIMPLIFICATION
- 5.4 AUTOMATIC SIMPLIFICATION
- 5.5 A SIMPLIFICATION ALGORITHM
- 5.6 SIMPLIFYING USER INTERACTION
- 5.7 RANDOM INPUT SIMPLIFIED
- 5.8 SIMPLIFYING FASTER
- 5.9 CONCEPTS
- 5.10 TOOLS
- 5.11 FURTHER READING
- Chapter 6: Scientific Debugging
- 6.1 HOW TO BECOME A DEBUGGING GURU
- 6.2 THE SCIENTIFIC METHOD
- 6.3 APPLYING THE SCIENTIFIC METHOD
- 6.4 EXPLICIT DEBUGGING
- 6.5 KEEPING A LOGBOOK
- 6.6 DEBUGGING QUICK-AND-DIRTY
- 6.7 ALGORITHMIC DEBUGGING
- 6.8 DERIVING A HYPOTHESIS
- 6.9 REASONING ABOUT PROGRAMS
- 6.10 CONCEPTS
- 6.11 FURTHER READING
- Chapter 7: Deducing Errors
- 7.1 ISOLATING VALUE ORIGINS
- 7.2 UNDERSTANDING CONTROL FLOW
- 7.3 TRACKING DEPENDENCES
- 7.4 SLICING PROGRAMS
- 7.5 DEDUCING CODE SMELLS
- 7.6 LIMITS OF STATIC ANALYSIS
- 7.7 CONCEPTS
- 7.8 TOOLS
- 7.9 FURTHER READING
- Chapter 8: Observing Facts
- 8.1 OBSERVING STATE
- 8.2 LOGGING EXECUTION
- 8.3 USING DEBUGGERS
- 8.4 QUERYING EVENTS
- 8.5 HOOKING INTO THE INTERPRETER
- 8.6 VISUALIZING STATE
- 8.7 CONCEPTS
- 8.8 TOOLS
- 8.9 FURTHER READING
- Chapter 9: Tracking Origins
- 9.1 REASONING BACKWARD
- 9.2 EXPLORING EXECUTION HISTORY
- 9.3 DYNAMIC SLICING
- 9.4 LEVERAGING ORIGINS
- 9.5 TRACKING DOWN INFECTIONS
- 9.6 CONCEPTS
- 9.7 TOOLS
- 9.8 FURTHER READING
- Chapter 10: Asserting Expectations
- 10.1 AUTOMATING OBSERVATION
- 10.2 BASIC ASSERTIONS
- 10.3 ASSERTING INVARIANTS
- 10.4 ASSERTING CORRECTNESS
- 10.5 ASSERTIONS AS SPECIFICATIONS
- 10.6 FROM ASSERTIONS TO VERIFICATION
- 10.7 REFERENCE RUNS
- 10.8 SYSTEM ASSERTIONS
- 10.9 CHECKING PRODUCTION CODE
- 10.10 CONCEPTS
- 10.11 TOOLS
- 10.12 FURTHER READING
- Chapter 11: Detecting Anomalies
- 11.1 CAPTURING NORMAL BEHAVIOR
- 11.2 COMPARING COVERAGE
- 11.3 STATISTICAL DEBUGGING
- 11.4 COLLECTING DATA IN THE FIELD
- 11.5 DYNAMIC INVARIANTS
- 11.6 INVARIANTS ON-THE-FLY
- 11.7 FROM ANOMALIES TO DEFECTS
- 11.8 CONCEPTS
- 11.9 TOOLS
- 11.10 FURTHER READING
- Chapter 12: Causes and Effects
- 12.1 CAUSES AND ALTERNATE WORLDS
- 12.2 VERIFYING CAUSES
- 12.3 CAUSALITY IN PRACTICE
- 12.4 FINDING ACTUAL CAUSES
- 12.5 NARROWING DOWN CAUSES
- 12.6 A NARROWING EXAMPLE
- 12.7 THE COMMON CONTEXT
- 12.8 CAUSES IN DEBUGGING
- 12.9 CONCEPTS
- 12.10 FURTHER READING
- Chapter 13: Isolating Failure Causes
- 13.1 ISOLATING CAUSES AUTOMATICALLY
- 13.2 ISOLATING VERSUS SIMPLIFYING
- 13.3 AN ISOLATION ALGORITHM
- 13.4 IMPLEMENTING ISOLATION
- 13.5 ISOLATING FAILURE-INDUCING INPUT
- 13.6 ISOLATING FAILURE-INDUCING SCHEDULES
- 13.7 ISOLATING FAILURE-INDUCING CHANGES
- 13.8 PROBLEMS AND LIMITATIONS
- 13.9 CONCEPTS
- 13.10 TOOLS
- 13.11 FURTHER READING
- Chapter 14: Isolating Cause–Effect Chains
- 14.1 USELESS CAUSES
- 14.2 CAPTURING PROGRAM STATES
- 14.3 COMPARING PROGRAM STATES
- 14.4 ISOLATING RELEVANT PROGRAM STATES
- 14.5 ISOLATING CAUSE–EFFECT CHAINS
- 14.6 ISOLATING FAILURE-INDUCING CODE
- 14.7 ISSUES AND RISKS
- 14.8 CONCEPTS
- 14.9 TOOLS
- 14.10 FURTHER READING
- Chapter 15: Fixing the Defect
- 15.1 LOCATING THE DEFECT
- 15.2 FOCUSING ON THE MOST LIKELY ERRORS
- 15.3 VALIDATING THE DEFECT
- 15.4 CORRECTING THE DEFECT
- 15.5 WORKAROUNDS
- 15.6 CONCEPTS
- 15.7 FURTHER READING
- Chapter 16: Learning from Mistakes
- 16.1 WHERE THE DEFECTS ARE
- 16.2 MINING THE PAST
- 16.3 WHERE DEFECTS COME FROM
- 16.4 ERRORS DURING SPECIFICATION
- 16.5 ERRORS DURING PROGRAMMING
- 16.6 ERRORS DURING QUALITY ASSURANCE
- 16.7 PREDICTING PROBLEMS
- 16.8 FIXING THE PROCESS
- 16.9 CONCEPTS
- 16.10 FURTHER READING
- APPENDIX: Formal Definitions
- GLOSSARY
- BIBLIOGRAPHY
- INDEX
- No. of pages: 544
- Language: English
- Edition: 2
- Published: June 12, 2009
- Imprint: Morgan Kaufmann
- Paperback ISBN: 9780123745156
- eBook ISBN: 9780080923000
AZ
Andreas Zeller
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.
Affiliations and expertise
Saarland University, Saarbruecken, GermanyRead Why Programs Fail on ScienceDirect