
Why programs fail
Andreas Zeller · 2005
Programming and computer science › Programmer careers and interviews
#4,889 most recommended
Hacker News
9
mentions by 8 people · top 32% of 15,732 books
Open Library
—
No ratings yet
2 want to read
Wikipedia
—
No article yet
About the book
A textbook on finding and fixing the causes of software failures. It treats debugging as a process that runs from reproducing a failure, through locating the defect that produced it, to verifying the fix, and it covers techniques for working through that process in real programs. The central claim is that debugging should follow the scientific method: observe the failure, form hypotheses about its cause, and test them with controlled experiments instead of relying on guesses. The book argues that several steps can be systematized or automated, including reducing a failing input to a minimal failure-inducing case, tracing the chain of infected states back from the failure to its origin, and correlating failing and passing runs to locate suspicious code. These are presented as techniques a programmer can apply directly.
Written by Claude from what it knows of this book.
What Hacker News says 88% recommend · 0% critical
In the commenters’ own words
Hey HN, Software Debugging is to me the funnest part of software development, and it occurred to me to write a book on it, adding some of my experience to the…
I was just reading the editorial reviews for the "Why Programs Fail" [0] that you recommended and couldn't agree more with this statement: "Today every…
What Open Library readers say
No Open Library reader has rated it yet.
- 2 want to read
- 0 reading
- 0 have read
What critics say, via Wikipedia
No Wikipedia article about this book yet, so no critics to quote.
Reddit communities — coming later
The threads it came up in
Details
- First published
- 2005
- ISBN
- 9781558608665
- Editions known
- 8 at Open Library
- Open Library
- OL5848374W
Debugging in computer science
Read next: its neighbours on the mosaic
Software VisualizationStephan Diehl · 2002 · recommended by 1 person · similar by subject and what people say about it
DebuggingDavid J. Agans · 2002 · recommended by 17 people · similar by subject and what people say about it
If I only changed the software, why is the phone on fire?Lisa Simone · 2007 · recommended by 1 person · similar by subject and what people say about it
Mechanizing ProofDonald MacKenzie · 2001 · recommended by 1 person · loosely similar by subject
Compiler design in CAllen I. Holub · 1990 · recommended by 11 people · similar by subject and what people say about it
Effective DebuggingDiomidis Spinellis · 2016 · recommended by 2 people · similar by subject and what people say about it
Advanced windows debuggingMario Hewardt · 2007 · recommended by 5 people · similar by subject and what people say about it
Debugging applicationsRobbins, John · 2000 · recommended by 4 people · similar by subject and what people say about it
A retargetable C compilerChristopher W. Fraser · 1995 · recommended by 9 people · loosely similar by subject
The logic of failureDietrich Dörner · 1996 · recommended by 15 people · similar by subject and what people say about it
A discipline of programmingEdsger Wybe Dijkstra · 1976 · recommended by 16 people · similar by subject and what people say about it
The Practice of ProgrammingBrian W. Kernighan · 1999 · recommended by 90 people · similar by subject and what people say about it
The Science of ProgrammingDavid Gries · 1989 · recommended by 9 people · similar by subject and what people say about it
Debugging the development processSteve Maguire · 1994 · recommended by 6 people · similar by subject and what people say about it
Writing solid codeSteve Maguire · 1993 · recommended by 18 people · similar by subject and what people say about it
The art of debugging with GDB, DDD, and EclipseNorman S. Matloff · 2008 · recommended by 2 people · similar by subject and what people say about it
Coders at WorkPeter Seibel · 2009 · recommended by 126 people · similar by subject and what people say about it
97 Things Every Programmer Should KnowKevlin Henney · 2010 · recommended by 6 people · similar by subject and what people say about it
C Traps and PitfallsAndrew Koenig · 1989 · recommended by 19 people · similar by subject and what people say about it
Debugging TeamsBrian W. Fitzpatrick · 2015 · recommended by 4 people · similar by subject and what people say about it
Advanced .NET debuggingMario Hewardt · 2009 · recommended by 3 people · similar by subject and what people say about it
Think like a ProgrammerV. Anton Spraul · 2012 · recommended by 2 people · similar by subject and what people say about it
Art of Programming - Volume 3 - Answers to ExercisesDonald Knuth · recommended by 6 people · similar by subject and what people say about it
The IDA Pro bookChris Eagle · 2008 · recommended by 5 people · similar by subject and what people say about it