More Web Proxy on the site http://driver.im/

research-article

Diagnose crashing faults on production software

Author:

Rongxin WuAuthors Info & Claims

FSE 2014: Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering

Pages 771 - 774

https://doi.org/10.1145/2635868.2666601

Published: 11 November 2014 Publication History

Abstract

Software crashes are severe manifestations of software faults. Especially, software crashes in production software usually result in bad user experiences. Therefore, crashing faults mostly are required to be fixed with a high priority. Diagnosing crashing faults on production software is non-trivial, due to the characteristics of production environment. In general, it is required to address two major challenges. First, crash reports in production software are usually numerous, since production software is used by a large number of end users in various environments and configurations. Especially, a single fault may manifest as different crash reports, which makes the prioritizing debugging and understanding faults difficult. Second, deployed software is required to run with minimal overhead and cannot afford a heavyweight instrumentation approach to collect program execution information. Furthermore, end users require that the logged information should not reveal sensitive production data. This thesis contributes for developing crashing fault diagnosis tools that can be used in production environment.

References

[1]

R. Abreu, P. Zoeteweij, and A. J. Van Gemund. On the accuracy of spectrum-based fault localization. In Testing: Academic and Industrial Conference Practice and Research Techniques-MUTATION, 2007. TAICPART-MUTATION 2007, pages 89–98. IEEE, 2007.

Digital Library

[2]

Apple. ”technical note tn2123: Crashreporter”, developer.apple.com/library/mac/#technotes/tn2004/ tn2123.html, 2010.

[3]

S. Artzi, J. Dolby, F. Tip, and M. Pistoia. Directed test generation for effective fault localization. In Proceedings of the 19th international symposium on Software testing and analysis, pages 49–60. ACM, 2010.

Digital Library

[4]

S. Artzi, J. Dolby, F. Tip, and M. Pistoia. Practical fault localization for dynamic web applications. In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering-Volume 1, pages 265–274. ACM, 2010.

Digital Library

[5]

S. Artzi, S. Kim, and M. D. Ernst. Recrash: Making software failures reproducible by preserving object states. In ECOOP 2008–Object-Oriented Programming, pages 542–565. Springer, 2008.

Digital Library

[6]

J. Bell, N. Sarda, and G. Kaiser. Chronicler: Lightweight recording to reproduce field failures. In Proceedings of the 2013 International Conference on Software Engineering, ICSE ’13, pages 362–371, Piscataway, NJ, USA, 2013. IEEE Press.

Digital Library

[7]

Y. Dang, R. Wu, H. Zhang, D. Zhang, and P. Nobel. Rebucket: A method for clustering duplicate crash reports based on call stack similarity. In Proceedings of the 2012 International Conference on Software Engineering, pages 1084–1093. IEEE Press, 2012.

Digital Library

[8]

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 Proceedings of the ACM SIGOPS 22Nd Symposium on Operating Systems Principles, SOSP ’09, pages 103–116, New York, NY, USA, 2009. ACM.

Digital Library

[9]

L. Jiang and Z. Su. Context-aware statistical debugging: from bug predictors to faulty control flow paths. In Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering, pages 184–193. ACM, 2007.

Digital Library

[10]

W. Jin and A. Orso. Bugredux: reproducing field failures for in-house debugging. In Proceedings of the 2012 International Conference on Software Engineering, pages 474–484. IEEE Press, 2012.

Digital Library

[11]

W. Jin and A. Orso. F3: Fault localization for field failures. In Proceedings of the 2013 International Symposium on Software Testing and Analysis, ISSTA 2013, pages 213–223, New York, NY, USA, 2013. ACM.

Digital Library

[12]

S. Kim, T. Zimmermann, and N. Nagappan. Crash graphs: An aggregated view of multiple crashes to improve crash triage. In Dependable Systems & Networks (DSN), 2011 IEEE/IFIP 41st International Conference on, pages 486––493. IEEE, 2011.

Digital Library

[13]

B. Liblit, M. Naik, A. X. Zheng, A. Aiken, and M. I. Jordan. Scalable statistical bug isolation. In ACM SIGPLAN Notices, volume 40, pages 15–26. ACM, 2005.

Digital Library

[14]

N. Modani, R. Gupta, G. M. Lohman, T. F. Syeda-Mahmood, and L. Mignet. Automatically identifying known software problems. In ICDE Workshops, pages 433–441. Citeseer, 2007.

Digital Library

[15]

Mozilla. ”mozilla crash reports”, http://crashstats.mozilla.com, 2012.

[16]

A. Schroter, N. Bettenburg, and R. Premraj. Do stack traces help developers fix bugs? In Mining Software Repositories (MSR), 2010 7th IEEE Working Conference on, pages 118–121. IEEE, 2010.

[17]

R. Wu, H. Zhang, S. C. Cheung, and S. Kim. Crashlocator: Locating crashing faults based on crash stacks. In Proceedings of the 2014 International Symposium on Software Testing and Analysis, 2014.

Digital Library

[18]

H. Zhang. An investigation of the relationships between lines of code and defects. In ICSM 2009, pages 274–283. IEEE, 2009.

Cited By

An LKhomh FGuéhéneuc Y(2018)An empirical study of crash-inducing commits in Mozilla FirefoxSoftware Quality Journal10.1007/s11219-017-9361-y26:2(553-584)Online publication date: 1-Jun-2018
https://dl.acm.org/doi/10.1007/s11219-017-9361-y
Bianchi FPezzè MTerragni VBodden ESchäfer WDeursen AZisman A(2017)Reproducing concurrency failures from crash stacksProceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering10.1145/3106237.3106292(705-716)Online publication date: 21-Aug-2017
https://dl.acm.org/doi/10.1145/3106237.3106292
Zagieboylo DZaman KBinder WCortellessa VKoziolek ASmirni EPoess M(2017)Cost-Efficient and Reliable Reporting of Highly Bursty Video Game Crash DataProceedings of the 8th ACM/SPEC on International Conference on Performance Engineering10.1145/3030207.3044529(201-212)Online publication date: 17-Apr-2017
https://dl.acm.org/doi/10.1145/3030207.3044529
Show More Cited By

Index Terms

Diagnose crashing faults on production software
1. Software and its engineering
  1. Software creation and management
    1. Software verification and validation
      1. Software defect analysis
        Software testing and debugging

Recommendations

ChangeLocator: locate crash-inducing changes based on crash reports
ICSE '18: Proceedings of the 40th International Conference on Software Engineering

Software crashes are severe manifestations of software bugs. Debugging crashing bugs is tedious and time-consuming. Understanding software changes that induce a crashing bug can provide useful contextual information for bug fixing and is highly demanded ...
CrashLocator: locating crashing faults based on crash stacks
ISSTA 2014: Proceedings of the 2014 International Symposium on Software Testing and Analysis

Software crash is common. When a crash occurs, software developers can receive a report upon user permission. A crash report typically includes a call stack at the time of crash. An important step of debugging a crash is to identify faulty functions, ...
ChangeLocator: locate crash-inducing changes based on crash reports

Software crashes are severe manifestations of software bugs. Debugging crashing bugs is tedious and time-consuming. Understanding software changes that induce a crashing bug can provide useful contextual information for bug fixing and is highly demanded ...

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences

FSE 2014: Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering

November 2014

856 pages

ISBN:9781450330565

DOI:10.1145/2635868

General Chair:
Shing-Chi Cheung
Hong Kong University of Science and Technology, China
,
Program Chairs:
Alessandro Orso
Georgia Institute of Technology, USA
,
Margaret-Anne Storey
University of Victoria, Canada

Copyright © 2014 ACM.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

SIGSOFT: ACM Special Interest Group on Software Engineering

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 11 November 2014

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Research-article

Conference

SIGSOFT/FSE'14

Sponsor:

SIGSOFT

SIGSOFT/FSE'14: 22nd ACM SIGSOFT Symposium on the Foundations of Software Engineering

November 16 - 21, 2014

Hong Kong, China

Acceptance Rates

Overall Acceptance Rate 17 of 128 submissions, 13%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

4
Total Citations
View Citations
326
Total Downloads

Downloads (Last 12 months)13
Downloads (Last 6 weeks)3

Reflects downloads up to 01 Jan 2025

Other Metrics

View Author Metrics

Citations

Cited By

An LKhomh FGuéhéneuc Y(2018)An empirical study of crash-inducing commits in Mozilla FirefoxSoftware Quality Journal10.1007/s11219-017-9361-y26:2(553-584)Online publication date: 1-Jun-2018
https://dl.acm.org/doi/10.1007/s11219-017-9361-y
Bianchi FPezzè MTerragni VBodden ESchäfer WDeursen AZisman A(2017)Reproducing concurrency failures from crash stacksProceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering10.1145/3106237.3106292(705-716)Online publication date: 21-Aug-2017
https://dl.acm.org/doi/10.1145/3106237.3106292
Zagieboylo DZaman KBinder WCortellessa VKoziolek ASmirni EPoess M(2017)Cost-Efficient and Reliable Reporting of Highly Bursty Video Game Crash DataProceedings of the 8th ACM/SPEC on International Conference on Performance Engineering10.1145/3030207.3044529(201-212)Online publication date: 17-Apr-2017
https://dl.acm.org/doi/10.1145/3030207.3044529
An LKhomh FBener AMinku LTurhan B(2015)An Empirical Study of Crash-inducing Commits in Mozilla FirefoxProceedings of the 11th International Conference on Predictive Models and Data Analytics in Software Engineering10.1145/2810146.2810152(1-10)Online publication date: 21-Oct-2015
https://dl.acm.org/doi/10.1145/2810146.2810152

View Options

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents