Why Programs Fail: A Guide to Systematic Debugging

By Andreas Zeller. 2005

520 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/e2054d37142d468f748453a0f5339ffd00dfc9b5

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

1. W. E. Wong
2. Sunghun Kim
3. Jaechang Nam
4. Ruizhi Gao
5. Gaeul Jeong
6. Yihao Li
7. Dongsun Kim
8. Thomas Zimmermann

Citations in the corpus

• RepairAgent: An Autonomous, LLM-Based Agent for Program Repair (2024, unknown): “Furthermore, we remind the agent how many cycles have already been executed, and how many cycles are left.”
• Automatic patch generation learned from human-written patches (2013, background): “Patch generation is an essential software maintenance task, since most software systems inevitably have bugs that need to be fixed [1], [2].”
• Debugging Machine Learning Tasks (2016, background): “Next, Alice turns to experimental approaches to answering why the classifier h ( · ) classifies the car x ∆ as an animal [11].”
• Improving bug triage with bug tossing graphs (2009, methodology): “This practice is not described in the Zeller's lifecycle [30], and we revise it by adding the TOSSED cycle in Figure 1.”
• A Survey on Software Fault Localization (2016, methodology): “Algorithmic debugging (also called declarative debugging), first discussed in Shapiro’s dissertation [325] with more details in [328], [402], decomposes a complex computation into a series of sub-computations to help locate program bugs.”
• When and Why Your Code Starts to Smell Bad (and Whether the Smells Go Away) (2017, unknown): “Also, as discussed by Zeller in his book Why programs fail , more experienced developers tend to perform more complex and critical tasks [92].”
• Best Practices for Scientific Computing (2012, background): “Debuggers are usually more productive than adding and removing print statements or scrolling through hundreds of lines of log output [67], because they allow the user to see exactly how the code is executing rather than just snapshots of state of the program at a few moments in time.”
• Duplicate bug reports considered harmful … really? (2008, background): “1This paper’s terminology follows Zeller [23] and Runeson et al.”
• A model for spectra-based software diagnosis (2011, methodology): “The Delta debugging paradigm [Zeller 2001; Cleve and Zeller 2005; Zeller 2006] is very effective at diagnosing certain classes of bugs.”