Why Programs Fail: A Guide to Systematic Debugging

Why Programs Fail: A Guide to Systematic Debugging

Volumn , Issue , 2005, Pages 1-448

  Zeller, Andreas ^a  

^a SAARLAND UNIVERSITY   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85152836855     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1016/B978-1-55860-866-5.X5000-0     Document Type: Book

References (138)

1. H. Agrawal and J.R. Horgan (1990) Dynamic Program Slicing. Proceedings of the ACM SIGPLAN 1990 Conference on Programming Language Design and Implementation (PLDI) ACM SIGPLAN Notices White Plains 246-256. (6)
2. A.V. Aho, R. Sethi and J.D. Ullman (1986) Compilers—Principles, Techniques and Tools. Reading, Massachusetts: Addison-Wesley
3. G. Ammons, R. Bodik and J.R. Larus (2002) Mining Specifications. Proceedings of the ACM SIGPLAN/SIGACT Symposium on Principles of Programming Languages (POPL) Portland, Oregon
4. M. Barnett, R. DeLine, M. Fähndrich, K.R.M. Leino and W. Schulte (2004) Verification of Object-Oriented Programs with Invariants. Journal of Object Technology 3(6), 27-56. Special issue: ECOOP 2003 workshop on Formal Techniques for Java-like Programs
5. C.A. Barron (2000) High Tech's Missionaries of Sloppiness. Salon Magazine December 2000
6. H.G. Barrow and R.M. Burstall (1976) Subgraph Isomorphism, Matching Relational Structures and Maximal Cliques. Information Processing Letters 4(4), 83-84
7. B. Beizer (1990) Software Testing Techniques. Boston, Massachusetts: International Thomson Computer Press
8. B. Beizer (1999) Unbanning the ‘Bug’. Posting 79q48l$ncc$1@fir.prod.itd.earthlink.net to comp.software.testing
9. B. Beizer (2000) Definition of the word bug. Posting 8kcV4.4008$S31.103769@newsread2.prod.itd.earthlink.net to comp.software.testing
10. W.I.B. Beveridge (1957) The Art of Scientific Investigation. 3d ed. New York: Vintage Books
11. D. Binkley and M. Harman (2003) A Large-scale Empirical Study of Forward and Backward Static Slice Size and Context Sensitivity. ICSM '03: Proceedings of the International Conference on Software Maintenance IEEE Computer Society
12. A. Bloch (Eds) (1980) Murphy's Law Book Two: More Reasons Why Things Go Wrong! Price/Stern/Sloan Publishers
13. G. Booch (1994) Object-oriented Analysis and Design. 2d ed. Reading, Massachusetts: Addison-Wesley
14. C. Bron and J. Kerbosch (1973) Algorithm 457—Finding All Cliques of an Undirected Graph. Communications of the ACM 16(9), 575-577
15. Y. Brun and M. Ernst (2004) Finding Latent Code Errors via Machine Learning over Program Executions. Proceedings of the International Conference on Software Engineering (ICSE) 480-490. Edinburgh, Scotland
16. L. Burdy, Y. Cheon, D. Cok, M. Ernst, J. Kiniry, G.T. Leavens, K.R.M. Leino and E. Poll (2003) An Overview of JML Tools and Applications. Proceedings of the Eighth International Workshop on Formal Methods for Industrial Critical Systems (FMICS 03) Trondheim, Norway
17. F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad and M. Stal (1996) Pattern-Oriented Software Architecture: A System of Patterns, volume 1 of Pattern-Oriented Software Architecture. New York: John Wiley & Sons
18. S. Chaki, A. Groce and O. Strichman (2004) Explaining Abstract Counterexamples. SIGSOFT '04/FSE-12: Proceedings of the 12th ACM SIGSOFT International Symposium on Foundations of Software Engineering Newport Beach, California: ACM Press 73-82
19. B. Chelf (2004) Squashing Bugs at the Source. Linux Magazine 55 16-20
20. J.-D. Choi and H. Srinivasan (1998) Deterministic Replay of Java Multithreaded Applications. Proceedings of the ACM SIGMETRICS Symposium on Parallel and Distributed Tools (SPDT) 48-59
21. J.-D. Choi and A. Zeller (2002) Isolating Failure-inducing Thread Schedules. Proceedings of the International Symposium on Software Testing and Analysis (ISSTA) 201-220. Rome, Italy
22. H. Cleve and A. Zeller (2005) Locating Causes of Program Failures. Proceedings of the International Conference on Software Engineering (ICSE) St. Louis, Missouri
23. R. Cohn and R. Muth (2004) Pin 2.0 User Guide. http://rogue.colorado.edu/Pin/documentation.php
24. J. Condit, M. Harren, S. McPeak, G.C. Necula and W. Weimer (2003) Ccured in the Real World. PLDI '03: Proceedings of the ACM SIGPLAN 2003 Conference on Programming Language Design and Implementation San Diego, California: ACM Press 232-244
25. V. Dallmeier, C. Lindig and A. Zeller (2005) Lightweight Defect Localization for Java. Proceedings of the 19th European Conference on Object-Oriented Programming Glasgow, Scotland
26. R.A. DeMillo, H. Pan and E.H. Spafford (1996) Critical Slicing for Software Fault Localization. Proceedings of the of the 1996 International Symposium on Software Testing and Analysis (ISSTA) ACM SIGSOFT 121-134
27. B. Demsky and M. Rinard (2003) Automatic Detection and Repair of Errors in Data Structures. Proceedings of the 18th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA) 78-95. Anaheim, California
28. W. Dickinson, D. Leon and A. Podgurski (2001) Finding Failures by Cluster Analysis of Execution Profiles. Proceedings of the International Conference on Software Engineering (ICSE) 339-348. Toronto, Ontario, Canada
29. E.W. Dijkstra (1972) Notes on Structured Programming. O.-J. Dahl, E.W. Dijkstra, C.A.R. Hoare,(Eds) Structured Programming London: Academic Press 1-82. Chapter 1
30. E.W. Dijkstra (1982) On Webster, Users, Bugs, and Aristotle. Selected Writings on Computing: A Personal Perspective New York: Springer-Verlag 288-291. Originally published as EWD 618 in 1977
31. E.W. Dijkstra (1989) On the Cruelty of Really Teaching Computer Science. Communications of the ACM 32(12), 1398-1404
32. M. Ducassé (1999) Coca: An Automated Debugger for C. Proceedings of the International Conference on Software Engineering (ICSE) 504-513. Los Angeles, California
33. G.W. Dunlap, S.T. King, S. Cinar, M.A. Basrai and P.M. Chen (2002) Revirt: Enabling Intrusion Analysis Through Virtual-machine Logging and Replay. Proceedings of the Symposium on Operating Systems Design and Implementation (OSDI) Boston, Massachusetts
34. E. Dustin, J. Rashka and J. Paul (2001) Automated Software Testing: Introduction, Management, and Performance. Reading, Massachusetts: Addison-Wesley
35. M. Eisenstadt (1997) My Hairiest Bug War Stories. Communications of the ACM 40(4), 30-37
36. M.D. Ernst, J. Cockrell, W.G. Griswold and D. Notkin (2001) Dynamically Discovering Likely Program Invariants to Support Program Evolution. IEEE Transactions on Software Engineering 27(2), 1-25
37. ESEC/FSE 99 (1999) Proceedings of ESEC/FSE'99 — 7th European Software Engineering Conference/7th ACM SIGSOFT Symposium on the Foundations of Software Engineering Lecture Notes in Computer Science Toulouse, France: Springer-Verlag
38. M. Fewster and D. Graham (1998) Software Test Automation. Reading, Massachusetts: Addison-Wesley
39. C. Fishman (1996) They Write the Right Stuff. Fast Company Magazine 06
40. P. Fritzson, N. Shahmehri, M. Kamkar and T. Gyimothy (1992) Generalized Algorithmic Debugging and Testing. ACM Letters on Programming Languages and Systems 1(4), 303-322
41. E. Gamma, R. Helm, R. Johnson and J. Vlissides (1994) Design Patterns: Elements of Reusable Object-Oriented Software. Reading, Massachusetts: Addison-Wesley
42. L. Geiger and A. Zündorf (2002) Graph-based Debugging with Fujaba. Workshop on Graph Based Tools, International Conference on Graph Transformations Barcelona, Spain
43. J.D. Gould (1975) Some Psychological Evidence on How People Debug Computer Programs. International Journal of Man-Machine Studies 7 151-182
44. T.L. Graves, A.F. Karr, J.S. Marron and H. Siy (2000) Predicting Fault Incidence Using Software Change History. IEEE Transactions on Software Engineering 26(7), 653-661
45. A. Groce and W. Visser (2003) What Went Wrong: Explaining Counterexamples. Proceedings of the SPIN Workshop on Model Checking of Software 121-135. Portland, Oregon
46. T. Gyimóthy, Á. Beszédes and I. Forgács (1999) An Efficient Relevant Slicing Method for Debugging. ESEC/FSE 99 1999 303-321
47. B. Hailpern and P. Santhanam (2002) Software Debugging, Testing, and Verification. IBM Systems Journal 41(1), 4-12
48. S. Hangal and M.S. Lam (2002) Tracking Down Software Bugs Using Automatic Anomaly Detection. ICSE-2002 2002 291-302
49. G.M. Hopper (1981) The First Bug. Annals of the History of Computing 3(3), 285-286
50. D. Hovemeyer and W. Pugh (2004) Finding Bugs Is Easy. Proceedings of the Conference on Object-Oriented Programming Systems Languages and Applications (OOPSLA) 132-136. Vancouver, Canada
51. D. Hume (1748) An Enquiry Concerning Human Understanding. London: A. Millar
52. W.S. Humphrey (1996) Introduction to the Personal Software Process. Reading, Massachusetts: Addison-Wesley
53. W.S. Humphrey (1999) Bugs or Defects? Carnegie Mellon Software Engineering Institute Technical Report Vol. 2, Issue 1
54. ICSE 2002 (2002) Proceedings of the International Conference on Software Engineering (ICSE) Orlando, Florida
55. J. Jacky (1996) The Way of Z: Practical Programming with Formal Methods. Cambridge, England: Cambridge University Press
56. T. Jim, J.G. Morrisett, D. Grossman, M.W. Hicks, J. Cheney and Y. Wang (2002) Cyclone: A Safe Dialect of C. Proceedings of the General Track: 2002 USENIX Annual Technical Conference USENIX Association 275-288
57. J.A. Jones, M.J. Harrold and J. Stasko (2002) Visualization of Test Information to Assist Fault Localization. ICSE 2002 2002 467-477
58. C. Kaner, J. Falk and H.Q. Nguyen (1999) Testing Computer Software. New York: John Wiley & Sons
59. B.W. Kernighan and R. Pike (1999) The Practice of Programming. Reading, Massachusetts: Addison-Wesley
60. G. Kiczales, E. Hilsdale, J. Hugunin, M. Kersten, J. Palm and W.G. Griswold (2001) An Overview of AspectJ. Proceedings of the 15th European Conference on Object-Oriented Programming Budapest, Hungary Springer-Verlag 327-353
61. T. Kidder (1981) The Soul of a New Machine. New York: Atlantic Monthly Press
62. J.C. Knight and N.G. Leveson (1986) An Experimental Evaluation of the Assumption of Independence in Multiversion Programming. IEEE Transactions on Software Engineering 12(1), 96-109
63. A.J. Ko and B.A. Myers (2004) Designing the Whyline: A Debugging Interface for Asking Questions About Program Behavior. CHI '04: Proceedings of the 2004 Conference on Human Factors in Computing Systems Vienna, Austria New York: ACM Press 151-158
64. A.J. Ko and B.A. Myers (2005) A Framework and Methodology for Studying the Causes of Software Errors in Programming Systems. Journal of Visual Languages and Computing In press
65. A. Kolawa (2002) Using Bug-Tracking Systems as Idea Repositories. stickyminds.com
66. R. Konuru, H. Srinivasan and J.-D. Choi (2000) Deterministic Replay of Distributed Java Applications. Proceedings of the International Parallel and Distributed Processing Symposium (IPDPS) Cancun, Mexico
67. B. Korel and J. Laski (1990) Dynamic Slicing of Computer Programs. The Journal of Systems and Software 13(3), 187-195
68. C. Larman (2002) Applying UML and Patterns. Englewood Cliffs, New Jersey: Prentice-Hall
69. G.T. Leavens, A.L. Baker and C. Ruby (1999) JML: A Notation for Detailed Design. Behaviora; Specifications of Businesses and Systems Boston, Massachusetts: Kluwer Academic Publishers 175-188
70. G.T. Leavens and Y. Cheon (2004) Design by Contract with JML. Technical report, Iowa State University Available at http://www.jmlspecs.org/
71. R. Lencevicius (2000) Advanced Debugging Methods. Boston, Massachusetts: Kluwer Academic Publishers
72. N.G. Leveson, S.S. Cha, J.C. Knight and T.J. Shimeall (1990) The Use of Self-Checks and Voting in Software Error Detection: An Empirical Study. IEEE Transactions on Software Engineering 16(4), 432-443
73. B. Lewis (2003) Debugging Backward in Time. M. Ronsse,(Eds) Proceedings of the Fifth International Workshop on Automated and Algorithmic Debugging (AADEBUG) Ghent, Belgium
74. D. Lewis (1973) Causation. Journal of Philosophy 70 556-567. Reprinted in Lewis (1986)
75. D. Lewis (1986) Philosophical Papers: Volume II. Oxford, England: Oxford University Press
76. B. Liblit, A. Aiken, A.X. Zheng and M.I. Jordan (2003) Bug Isolation via Remote Program Sampling. Proceedings of the SIGPLAN 2003 Conference on Programming Language Design and Implementation (PLDI) San Diego, Californa
77. B. Liblit, M. Naik, A.X. Zheng, A. Aiken and M.I. Jordan (2005) Scalable Statistical Bug Isolation. Proceedings of the SIGPLAN 2005 Conference on Programming Language Design and Implementation (PLDI) Chicago, Illinois
78. R.C. Martin (1996) The Dependency Inversion Principle. C++ Report May 8, 1996
79. S.C. McConnell (1993) Code Complete: A Practical Handbook of Software Construction. Redmond, Washington: Microsoft Press
80. B. Meyer (1997) Object-Oriented Software Construction. 2d ed. Englewood Cliffs, New Jersey: Prentice-Hall
81. B.P. Miller, L. Fredrikson and B. So (1990) An Empirical Study of the Reliability of UNIX Utilities. Communications of the ACM 33(12), 32-44
82. B. Mirrer (2000) Organize Your Problem Tracking System. Software Testing & Quality Engineering (STQE) Magazine 2(5)
83. A. Mockus and L.G. Votta (2000) Identifying Reasons for Software Changes Using Historic Databases. Proceedings of the International Conference on Software Maintenance (ICSM 2000) San Jose, California: IEEE Computer Society 120-130
84. A. Mockus and D.M. Weiss (2000) Predicting Risk of Software Changes. Bell Labs Technical Journal 5(2), 169-180
85. C. Morgenstern (1964) The Impossible Fact. M. Knight,(Eds) The Gallows Songs Berkeley, California: University of California Press Original poem published in 1905
86. S.S. Muchnik (1997) Advanced Compiler Design and Implementation. San Francisco, California: Morgan Kaufmann
87. M.M. Müller, R. Typke and O. Hagner (2002) Two Controlled Experiments Concerning the Usefulness of Assertions as a Means for Programming. Proceedings of the 18th International Conference on Software Maintenance (ICSM 2002) San Jose, California: IEEE Computer Society 84-92
88. G.J. Myers (1979) The Art of Software Testing. New York: John Wiley & Sons
89. L. Naish (1997) A Declarative Debugging Scheme. The Journal of Functional and Logic Programming (3), 1997
90. G.C. Necula, S. McPeak and W. Weimer (2002) Ccured: Type-Safe Retrofitting of Legacy Code. POPL '02: Proceedings of the 29th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages Portland, Oregon New York: ACM Press 128-139
91. B. Ness and V. Ngo (1997) Regression Containment Through Source Code Isolation. Proceeding of the 21st Annual International Computer Software & Applications Conference (COMPSAC '97) Washington, DC: IEEE Computer Society Press 616-621
92. N. Nethercote (2004) Dynamic Binary Analysis and Instrumentation. Ph.D. thesis, University of Cambridge, UK
93. N. Nethercote and J. Seward (2003) Valgrind: A Program Supervision Framework. Electronic Notes in Theoretical Computer Science 89(2)
94. M. Neuburg (2003) AppleScript: The Definitive Guide. Sebastopol, California: O'Reilly
95. A. Orso, T. Apiwattanapong and M.J. Harrold (2003) Leveraging Field Data for Impact Analysis and Regression Testing. ESEC/FSE-11: Proceedings of the 9th European Software Engineering Conference Held Jointly with 11th ACM SIGSOFT International Symposium on Foundations of Software Engineering New York: ACM Press 128-137
96. T. Ostrand and E. Weyuker (2002) The Distribution of Faults in a Large Industrial Software System. P.G. Frankl,(Eds) Proceedings of the ACM SIGSOFT 2002 International Symposium on Software Testing and Analysis (ISSTA-02) Software Engineering Notes New York: ACM Press 55-64. 4
97. T.J. Ostrand, E.J. Weyuker and R.M. Bell (2004) Where the Bugs Are. ISSTA '04: Proceedings of the 2004 ACM SIGSOFT International Symposium on Software Testing and Analysis New York: ACM Press 86-96
98. K.J. Ottenstein and L.M. Ottenstein (1984) The Program Dependence Graph in a Software Development Environment. Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments ACM SIGPLAN Notices 177-184
99. J. Pearl (2000) Causality: Models, Reasoning, and Inference. New York: Cambridge University Press
100. M. Pezzè and M. Young (2005) Software Testing and Analysis: Process, Principles, and Techniques. New York: John Wiley & Sons In press
101. R.M. Pirsig (1974) Zen and the Art of Motorcycle Maintenance. New York: William Morrow Publishers
102. A. Podgurski, D. Leon, P. Francis, W. Masri, M. Minch, J. Sun and B. Wang (2003) Automated Support for Classifying Software Failure Reports. ICSE '03: Proceedings of the 25th International Conference on Software Engineering Portland, Oregon: IEEE Computer Society 465-475
103. K. Popper (1959) The Logic of Scientific Discovery. London: Hutchinson Translation of Logik der Forschung, Vienna, Austria, 1935
104. R. Purushothaman and D.E. Perry (2004) Towards Understanding the Rhetoric of Small Changes. Proceedings of the International Workshop on Mining Software Repositories (MSR 2004) 90-94. Edinburgh, Scotland
105. E.S. Raymond (Eds) (1996) New Hacker's Dictionary 3rd ed. Cambridge, Massachusetts: MIT Press
106. M. Renieris and S.P. Reiss (2003) Fault Localization with Nearest Neighbor Queries. Proceedings of the 18th International Conference on Automated Software Engineering Montreal, Canada
107. M. Ronsse, K.D. Bosschere, M. Christiaens, J.C. de Kergommeaux and D. Kranzlmüller (2003) Record/Replay for Nondeterministic Program Executions. Communications of the ACM 46(9), 62-67
108. J.B. Rosenberg (1996) How Debuggers Work—Algorithms, Data Structures, and Architecture. New York: John Wiley & Sons
109. RTI (2002) The Economic Impacts of Inadequate Infrastructure for Software Testing. Technical Report, Planning Report 02-3 National Institute of Standards & Technology
110. D. Saff and M. Ernst (2004) Automatic Mock Object Creation for Test Factoring. C. Flanagan, A. Zeller,(Eds) Proceedings of the ACM SIGPLAN/SIGSOFT Workshop on Program Analysis for Software Tools and Engineering (PASTE) Washington, DC
111. D. Saff and M. Ernst (2004) An Experimental Evaluation of Continuous Testing During Development. ISSTA 2004, Proceedings of the 2004 International Symposium on Software Testing and Analysis 76-85. Boston, Massachusetts
112. D.C. Schmidt, M. Stal, H. Rohnert and F. Buschmann (2000) Pattern-Oriented Software Architecture: Patterns for Concurrent and Networked Objects, volume 2 of Pattern-Oriented Software Architecture. New York: John Wiley & Sons
113. E.Y. Shapiro (1982) Algorithmic Program Debugging. Ph.D. thesis, MIT Press. ACM Distinguished Dissertation
114. F.R. Shapiro (1994) Exposing the Myth Behind the First Bug Reveals a Few Tales. BYTE
115. J. Shore (2004) Fail Fast. IEEE Software 21(5), 21-25
116. J. Śliwerski, T. Zimmermann and A. Zeller (2005) When Do Changes Induce Fixes? Proceedings of the Workshop on Mining Software Repositories (MSR) St. Louis
117. I. Sommerville (2001) Software Engineering. 6th ed. Reading, Massachusetts: Addison-Wesley
118. R. Sosič and D. Abramson (1997) Guard: A Relative Debugger. Software—Practice and Experience 27(2), 106-185
119. R.M. Stallman and R.H. Pesch (1994) Debugging with GDB. 4th ed. Free Software Foundation Distributed with GDB 4.13
120. F. Tip (1995) A Survey of Program Slicing Techniques. Journal of Programming Languages 3(3), 121-189
121. J. Viega and G. McGraw (2001) Building Secure Software. Reading, Massachusetts: Addison-Wesley
122. J.M. Voas (1992) PIE: A Dynamic Failure-based Technique. IEEE Transactions on Software Engineering 18(8), 717-727
123. R. Wahbe (1992) Efficient Data Breakpoints. ASPLOS-V: Proceedings of the Fifth International Conference on Architectural Support for Programming Languages and Operating Systems New York: ACM Press 200-212
124. G.M. Weinberg (1971) The Psychology of Computer Programming. New York: Van Nostrand Reinhold
125. M. Weiser (1982) Programmers Use Slices When Debugging. Communications of the ACM 25(7), 446-452
126. M. Weiser (1984) Program Slicing. IEEE Transactions on Software Engineering 10(4), 352-357
127. D.B. Whalley (1994) Automatic Isolation of Compiler Errors. ACM Transactions on Programming Languages and Systems 16(5), 1648-1659
128. E.B. Wilson (1952) An Introduction to Scientific Research. New York: McGraw-Hill
129. Y. Xie and D. Engler (2002) Using Redundancies to Find Errors. SIGSOFT '02/FSE-10: Proceedings of the 10th ACM SIGSOFT Symposium on Foundations of Software Engineering New York: ACM Press 51-60
130. G.P. Zachary (1994) Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. New York: The Free Press
131. E.N. Zalta (Eds) (2000) Stanford Encyclopedia of Philosophy Stanford University
132. A. Zeller (1999) Yesterday, My Program Worked. Today, It Does Not. Why? ESEC/FSE 99 253-267. 1999
133. A. Zeller (2000) Debugging with DDD. version 3.2 edition Universität Passau and Free Software Foundation Distributed with GNU DDD
134. A. Zeller (2002) Isolating Cause-Effect Chains from Computer Programs. W.G. Griswold,(Eds) Proceedings of the Tenth ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-10) New York: ACM Press 1-10. Charleston, South Carolina
135. A. Zeller and R. Hildebrandt (2002) Simplifying and Isolating Failure-inducing Input. IEEE Transactions on Software Engineering 28(2), 183-200
136. A. Zeller and D. Lütkehaus (1996) DDD—A Free Graphical Front-end for UNIX Debuggers. SIGPLAN Notices 31(1), 22-27
137. X. Zhang and R. Gupta (2004) Cost-effective Dynamic Program Slicing. Proceedings of the 2004 ACM SIGPLAN Conference on Programming Language Design and Implementation (PLDI 2004) 94-106. Washington, DC
138. T. Zimmermann and A. Zeller (2002) Visualizing Memory Graphs. S. Diehl,(Eds) Proceedings of the International Dagstuhl Seminar on Software Visualization Lecture Notes in Computer Science Heidelberg: Springer-Verlag 191-204. Dagstuhl, Germany