BugRedux: Reproducing field failures for in-house debugging
The DOI matches its Crossref record; 34 of the 35 references it cites were found in a registry or an index.
Abstract
A recent survey conducted among developers of the Apache, Eclipse, and Mozilla projects showed that the ability to recreate field failures is considered of fundamental importance when investigating bug reports. Unfortunately, the information typically contained in a bug report, such as memory dumps or call stacks, is usually insufficient for recreating the problem. Even more advanced approaches for gathering field data and help in-house debugging tend to collect either too little information, and be ineffective, or too much information, and be inefficient. To address these issues, we present BugRedux, a novel general approach for in-house debugging of field failures. BugRedux aims to synthesize, using execution data collected in the field, executions that mimic the observed field failures. We define several instances of BugRedux that collect different types of execution data and perform, through an empirical study, a cost-benefit analysis of the approach and its variations. In the study, we apply BugRedux to 16 failures of 14 real-world programs. Our results are promising in that they show that it is possible to synthesize in-house executions that reproduce failures observed in the field using a suitable set of execution data.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“Bug reproduction is a critical step in investigating bug reports [Jin and Orso 2012], and is integrated into many recent software engineering agents [Arora et al. 2024;Factory 2024;Honeycomb 2024;MentatBot 2024;OpenDevin 2024;Ruan et al. 2024;Yang et al. 2024a].”
From Demystifying LLM-Based Software Engineering Agents (2025) · cites this paper as Jin and Orso 2012
Citations
Cites
Symbolic execution and program testing
King, J. C. (1976) · Communications of the ACM · doi:10.1145/360248.360252 · Cited by 3,031 · cited 1×
“In this work, we decided to use an approach based on symbolic execution [18].”
MethodKLEE: unassisted and automatic generation of high-coverage tests for complex systems programs
Cadar, C., Dunbar, D., & Engler, D. (2008) · doi:10.5555/1855741.1855756 · Cited by 2,620
DART: directed automated random testing
Godefroid, P., Klarlund, N., & Sen, K. (2005) · Proceedings of the 2005 ACM SIGPLAN conference on Programming language design and implementation · doi:10.1145/1065010.1065036 · Cited by 1,570 · cited 1×
“, [20], [27]–[29]) and random generation (e.”
Automated Whitebox Fuzz Testing.
Godefroid, P., Levin, M. Y., & Molnar, D. A. (2008) · Cited by 1,095
Simplifying and isolating failure-inducing input
Zeller, A., & Hildebrandt, R. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/32.988498 · Cited by 1,079 · cited 1×
“, [13], [14]), or are still in their early phase of development and in need of a more thorough”
BackgroundAre automated debugging techniques actually helping programmers?
Parnin, C., & Orso, A. (2011) · Proceedings of the 2011 International Symposium on Software Testing and Analysis · doi:10.1145/2001420.2001445 · Cited by 576 · cited 1×
“Although such an evaluation would be extremely useful, and we plan to do it in the future as we did for earlier work [26], we believe that it would be premature at this point.”
BackgroundSelf-citationExtracting usability information from user interface events
Hilbert, D. M., & Redmiles, D. F. (2000) · ACM Computing Surveys · doi:10.1145/371578.371593 · Cited by 477
Scalable statistical bug isolation
Liblit, B., Naik, M., Zheng, A. X., Aiken, A., & Jordan, M. I. (2005) · Proceedings of the 2005 ACM SIGPLAN conference on Programming language design and implementation · doi:10.1145/1065010.1065014 · Cited by 472 · cited 1×
“Among these techniques, some collect only limited amounts of information ( e.g., sampled branch profiles in the case of CBI [6], [7]).”
BackgroundA Theoretical and Empirical Study of Search-Based Testing: Local, Global, and Hybrid Search
Harman, M., & McMinn, P. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.71 · Cited by 400 · cited 1×
“, [38]), and techniques that take advantage of existing test inputs using some fort of fuzzing (e.”
BackgroundCompilers: Principles, Techniques, and Tools (2nd Edition)
Aho, A. V., Lam, M. S., Sethi, R., & Ullman, J. D. (2006) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 387
Research works printed but not linked: 9
- jin, 2011, BugRedux Reproducing Field Failures for In-house Debugging
- 2012, Tmin Fuzzing Test Case Optimizer
- 2012, The Amazing VM Record/Replay Feature in VMware Workstation 6
- 2012, Software-artifact infrastructure repository
- 2012, Breakpad
- lu, 0, BugBench: Benchmarks for Evaluating Bug Detection Tools, Workshop on the Evaluation of Software Defect Detection Tools 2005
- 2012, Technical Note TN2123 CrashReporter
- 2012, Windows Error Reporting Getting Started
- pacheco, 0, Randoop: Feedback-Directed Random Testing for Java, Proceedings of the 22nd ACM SIGPLAN Conference on Object-oriented Programming Systems and Applications 2007, 815
Cited by
Items 101–122 of 122
pbSE: Phase-Based Symbolic Execution
Xiao, Q., Chen, Y., Wu, C., Li, K., Mao, J., Guo, S., & Shi, Y. (2017) · International Conference on Dependable Systems & Networks/Proceedings · doi:10.1109/dsn.2017.48 · Cited by 2
“• KLEE, with its strong support for handling interactions with the external environment, for making input arguments and files symbolic, has been widely used in many research fields, including program analysis[6], [15], [18], software testing[8], [21], and software error detection[24], [7].”
MethodReproducing and debugging field failures in house
Jin, W. (2013) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2013.6606738 · Cited by 2
“BugRedux is presented in detail in Reference [17].”
BackgroundInfluentialSelf-citationBansal, K., Singh, G., Malik, S., & Rohil, H. (2023) · International Journal of Systems Assurance Engineering and Management · doi:10.1007/s13198-023-01902-7 · Cited by 2
“Jin and Orso (2012) established BugRedux, an approach to gather extra information from the buggy ground and transmits the collected information to developers for repeating the failure circumstance.”
BackgroundExperimental Fault Analysis Process Implemented Using Model Extraction and Model Checking
Ogawa, H., Ichii, M., Kumeno, F., & Aoki, T. (2015) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/compsac.2015.118 · Cited by 1
“BugRedux[20] is an in-house debugging approach of field failures.”
MethodReproducing and debugging field failures in house
Jin, W. (2013) · doi:10.5555/2486788.2487030 · Cited by 1
Self-citationDo Exceptional Behavior Tests Matter on Spectrum-Based Fault Localization?
Yoshioka, H., Higo, Y., Matsumoto, S., Kusumoto, S., Itoh, S., & Huyen, P. T. T. (2023) · Lecture notes in computer science · doi:10.1007/978-3-031-49266-2_28 · Cited by 1
LibAFL-DiFuzz: Advanced Architecture Enabling Directed Fuzzing
Parygina, D., Mezhuev, T., & Kuts, D. (2024) · Ivannikov ISPRAS Open Conference (ISPRAS) · doi:10.1109/ispras64596.2024.10899166 · Cited by 1
“Directed fuzzing [6], on the other hand, is much better when it comes to the tasks of patch testing [7], crash reproduction [8], and static analysis report verification [9].”
A Search-Based Framework for Failure Reproduction
Kifetew, F. M. (2012) · Lecture notes in computer science · doi:10.1007/978-3-642-33119-0_22 · Cited by 1
“For instance, Jin and Orso propose a customized SE-based algorithm for reproducing failures by using execution data collected from the field via instrumentation [9].”
MethodDifferentially-private software frequency profiling under linear constraints
Zhang, H., Hao, Y., Latif, S., Bassily, R., & Rountev, A. (2020) · Proceedings of the ACM on Programming Languages · doi:10.1145/3428271 · Cited by 3
“As other examples, remote run-time information can be utilized for performance analysis [Han et al. 2012; Nagpurkar et al. 2006], focused testing [Pavlopoulou and Young 1999], debugging [Liblit et al. 2003; Ohmann et al. 2017], and failure analysis [Clause and Orso 2007; Jin and Orso 2012].”
MethodSecuring software systems via fuzz testing and verification
Chen, H. (2019) · DR-NTU (Nanyang Technological University) · doi:10.32657/10356/136764
Binary-level Directed Symbolic Execution Through Pattern Learning
Zhang, Z., Chen, L., Wei, H., Dong, G., Zhang, Y., Nie, X., & Shi, G. (2022) · IEEE International Symposium on Parallel and Distributed Processing with Applications (ISPA) · doi:10.1109/ispa-bdcloud-socialcom-sustaincom57177.2022.00014
“The static analysis is performed to calculate the distance of control flow [2], [3], [6] or data flow [4].”
BackgroundMethodThe Comparative Evaluation of Test Prioritization Approaches in an Industrial Study
Ahmad, A., Neto, F. G. D. O., Enoiu, E. P., Sandahl, K., & Leifler, O. (2023) · IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C) · doi:10.1109/qrs-c60940.2023.00025 · Cited by 1
Goyal, A., & Sardana, N. (2024) · Procedia Computer Science · doi:10.1016/j.procs.2024.04.268
Anonymizing Test Data in Android: Does It Hurt?
Masserini, E., Ginelli, D., Micucci, D., Briola, D., & Mariani, L. (2024) · doi:10.1145/3644032.3644463
“Finally, some techniques addressed the problem of reproducing failures in Java, such as, BugRedux [10], JCHARMING [15], STAR [4], and EvoCrash [16].”
BackgroundMethodInfluentialSearch-based Crash Reproduction for Android Apps
Auer, M., Diner, D., & Fraser, G. (2024) · Genetic and Evolutionary Computation Conference (GECCO) · doi:10.1145/3638529.3654034
“The focus on GUI tests also distinguishes our work from prior work using symbolic execution [8, 17] and model checking [26].”
Automatically Learning a Precise Measurement for Fault Diagnosis Capability of Test Cases
Zhao, Y., Sun, Z., Wang, G., Liang, Q., Zhang, Y., Lou, Y., Hao, D., & Zhang, L. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3712189
Effective Seed Scheduling for Directed Fuzzing with Function Call Sequence Complexity Estimation
Peng, X., Jia, P., Fan, X., Huang, C., & Liu, J. (2025) · Applied Sciences · doi:10.3390/app15158345
Enhancing Symbolic Execution with Machine-Checked Safety Proofs
Trabish, D., & Itzhaky, S. (2026) · ACM SIGPLAN International Conference on Certified Programs and Proofs (CPP) · doi:10.1145/3779031.3779089
SpeedDGF: Path-Guided Byte Energy for Efficient Directed Grey-Box Fuzzing
Ding, Z., Wu, S., You, W., Zhu, L., & Zhang, Y. (2026) · Electronics · doi:10.3390/electronics15050913
Towards improving the quality of mobile app by leveraging crowdsourced feedback
Lacruz, M. G. (2016) · theses.fr (ABES) · doi:10.70675/79947114z9db5z41ebzb996z0f625c151519
From runtime failures to patches : study of patch generation in production
Durieux, T. (2018) · theses.fr (ABES) · doi:10.70675/e420845ezd509z45e1za0baz01c776105906
Metadata
- Authors
- Jin, W., & Orso, A.
- Affiliations
- Georgia Institute of Technology (US)
- ORCID
- Orso, Alessandro
- Venue
- 2012 34th International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2012-06
- Pages
- 474-484
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W3140804348
- Cited by
- 122
- References
- 35
- Citations by year
- 2026: 2 · 2025: 4 · 2024: 11 · 2023: 13 · 2022: 10 · 2021: 7 · 2020: 11 · 2019: 11 · 2018: 6 · 2017: 11 · 2016: 10 · 2015: 8 · 2014: 3 · 2013: 13 · 2012: 2
- FWCI
- 5.77
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Keywords
- field failures, insect reproduction, execution replay, bug reports, software debugging, cost-benefit analysis
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.