Fighting bugs: remove, retry, replicate, and rejuvenate

  title={Fighting bugs: remove, retry, replicate, and rejuvenate},
  author={Michael Grottke and Kishor S. Trivedi},
Even if software developers don't fully understand the faults or know their location in the code, software rejuvenation can help avoid failures in the presence of aging-related bugs. This is good news because reproducing and isolating an aging-related bug can be quite involved, similar to other Mandelbugs. Moreover, monitoring for signs of software aging can even help detect software faults that were missed during the development and testing phases. If, on the other hand, a developer can detect… CONTINUE READING
Highly Influential
This paper has highly influenced 19 other papers. REVIEW HIGHLY INFLUENTIAL CITATIONS
Highly Cited
This paper has 284 citations. REVIEW CITATIONS

From This Paper

Topics from this paper.


Publications citing this paper.
Showing 1-10 of 133 extracted citations

Keep it moving: Proactive workload management for reducing SLA violations in large scale SaaS clouds

2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE) • 2013
View 5 Excerpts
Highly Influenced

Achieving and assuring high availability

2008 IEEE International Symposium on Parallel and Distributed Processing • 2008
View 7 Excerpts
Highly Influenced

Experience Report: Fault Triggers in Linux Operating System: from Evolution Perspective

2017 IEEE 28th International Symposium on Software Reliability Engineering (ISSRE) • 2017
View 4 Excerpts
Highly Influenced

Recovery From Software Failures Caused by Mandelbugs

IEEE Transactions on Reliability • 2016
View 8 Excerpts
Method Support
Highly Influenced

FLAVS: A Fault Localization Add-In for Visual Studio

2015 IEEE/ACM 1st International Workshop on Complex Faults and Failures in Large Software Systems (COUFLESS) • 2015
View 3 Excerpts
Highly Influenced

285 Citations

Citations per Year
Semantic Scholar estimates that this publication has 285 citations based on the available data.

See our FAQ for additional information.