Do stack traces help developers fix bugs?

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2010, Pages 118-121

  Schröter, Adrian ^a   Bettenburg, Nicolas ^b   Premraj, Rahul ^c  

^a UNIVERSITY OF VICTORIA   (Canada)

^b QUEEN S UNIVERSITY   (Canada)

^c VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

Bug tracking; Collaboration; Debugging; Empirical study; Stack traces

Indexed keywords

BUG REPORTS; BUG TRACKING; BUG-FIXING; EMPIRICAL EVIDENCE; EMPIRICAL STUDIES; SOFTWARE VENDORS;

COMPUTER SOFTWARE;

PROGRAM DEBUGGING;

EID: 77953783353     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/MSR.2010.5463280     Document Type: Conference Paper

References (8)

1. N. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj, and T. Zimmermann, "What makes a good bug report?" in Procs of FSE. ACM, 2008, pp. 308-318.
2. Java, "Analyzing stack traces," http://java.sun.com/developer/ onlineTraining/Programming/JDCBook/stack.html, last accessed 2009-12-21.
3. J. Goerzen, "Finding stubborn bugs with meaningful debug info," Linux J., vol. 2005, no. 129, p. 7, 2005.
4. H. Shah, C. Görg, and M. J. Harrold, "Why do developers neglect exception handling?" in Procs. of the Int. Workshop on Exception Handling. ACM, 2008, pp. 62-68.
5. T. O. Allwood, S. Peyton Jones, and S. Eisenbach, "Finding the needle: stack traces for ghc," in Procs. of the Symposium on Haskell. ACM, 2009, pp. 129-140.
6. K. Glerum, K. Kinshumann, S. Greenberg, G. Aul, V. Orgovan, G. Nichols, D. Grant, G. Loihle, and G. Hunt, "Debugging in the (very) large: ten years of implementation and experience," in Procs. of the Symposium on Operating systems principles. ACM, 2009, pp. 103-116.
7. N. Bettenburg, R. Premraj, T. Zimmermann, and S. Kim, "Duplicate bug reports considered harmful?" in Procs. of ICSM. Beijing: IEEE, September 2008, pp. 337-345.
8. J. Śliwerski, T. Zimmermann, and A. Zeller, "When do changes induce fixes?" in Procs. of MSR. ACM, 2005, pp. 1-5.