Reproducibility of Environment-Dependent Software Failures: An Experience Report

Cavezza, Davide G.; Pietrantuono, Roberto; Alonso, Javier; Russo, Stefano; Trivedi, Kishor S.

doi:10.1109/issre.2014.19

Cited by 26 publications

(10 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The authors in [29] perform a classification of faults reported by the flight software used in all 18 JPL/NASA space missions: 36.5% of the analyzed bugs were Mandelbugs. Similar or higher percentages are reported in the open-source programs analyzed in [30], [31].…”

Section: Related Worksupporting

confidence: 81%

“…Table II. The non-aging related Mandelbugs could be removed once the cause was determined, aging-related Mandelbugs that result in performance degradation, and an ageing related bug leading to a system crash that had to be rectified by system parameter change. The three bugs listed by Cavezza et al are a delegate of the general classes of Mandelbugs [31]. For example, a lag issue in the system may cause uniformity issues.…”

Section: Google Security Researchmentioning

confidence: 99%

See 1 more Smart Citation

Analysis of bugs in Google security research project database

Rawal

Tsetse

2015

2015 IEEE Recent Advances in Intelligent Computational Systems (RAICS)

View full text Add to dashboard Cite

Several classifications exist in the literature on software bugs. Classification of bugs in software systems is primarily based on the level of complexity and reproducibility. Bohrbugs and Mandelbugs are the two most common bugs present in most software systems. This paper studies the distribution of Bohrbugs and Mandelbugs in the Google Security Research Project (GSRP) and some selected software systems. Also, we studied the frequency distribution of bug-fix time reported in GSRP. Bug-fix time analysis is a critical study of bug reporting systems and for measuring software quality. For example, if bugs in a complex software system take a relatively long time to be fixed, the system may have some structural problems that would make it difficult to reproduce the bugs. This paper reports the distribution of various bugs, and bug fix time statistics. We also list the top 25 bug-fix times reported in GSRP.

show abstract

Section: Related Worksupporting

confidence: 81%

Section: Google Security Researchmentioning

confidence: 99%

Analysis of bugs in Google security research project database

Rawal

Tsetse

2015

2015 IEEE Recent Advances in Intelligent Computational Systems (RAICS)

View full text Add to dashboard Cite

show abstract

“…Although the testing phase is not the final one, and more bugs of this type are expected to surface in later stages, our conjecture is confirmed by the high percentage of not tried or not available cases. Considering their high impact at operational time , this aspect should be improved. On single CSCIs, we observed again no significant correlation amongst the proportion of not always reproducible defects and any of the testing metrics.…”

Section: Resultsmentioning

confidence: 99%

Defect analysis in mission-critical software systems: a detailed investigation

Carrozza

Pietrantuono

Russo

2014

J. Softw. Evol. and Proc.

Self Cite

View full text Add to dashboard Cite

The practice of defect analysis is recognized as an essential task for software process measurement, yet its\ud effective application in the industrial development of large-scale software systems raises several challenges.\ud We report the results of a study conducted at SELEX ES - a large system integrator leader in the market of\ud software-intensive mission-critical systems. The article describes the defect analysis approach that we tailored to evaluate the software development process with respect to the quality of produced software and\ud its relation with the required effort. Three key phases of the process were addressed, regarding the software\ud implementation, the testing phase and the prerelease defect fixing activity, over a set of six computer software configuration items developed from 2009 to 2012 for the naval and maritime domain product line.\ud The analysis highlighted efficiency bottlenecks in each of the monitored phases, providing company engineers with insights about room for process improvement. The implemented approach, the observed phenomena and the inferred conclusions are of support to practitioners coping with systems, development models and\ud industrial environments similar to the considered one

show abstract

“…The study involves a qualitative analysis and documentation of 42 bugs from the Linux Kernel repository, and required an effort of several person-months. A third example is [17] on environment-dependent bugs in MySQL Server software. The authors extracted 7 hard-to-reproduce bugs from the manual analysis of 568 bug reports, and performed experimental test campaigns to study the influence of memory occupation, disk usage and level of concurrency on the failure reproducibility.…”

Section: Related Workmentioning

confidence: 99%

Can Robot Navigation Bugs Be Found in Simulation? An Exploratory Study

Sotiropoulos

Waeselynck

Guiochet

et al. 2017

2017 IEEE International Conference on Software Quality, Reliability and Security (QRS)

View full text Add to dashboard Cite

The ability to navigate in diverse and previously unknown environments is a critical service of autonomous robots. The validation of the navigation software typically involves test campaigns in the field, which are costly and potentially risky for the robot itself or its environment. An alternative approach is to perform simulation-based testing, by immersing the software in virtual worlds. A question is then whether the bugs revealed in real worlds can also be found in simulation. The paper reports on an exploratory study of bugs in an academic software for outdoor robots navigation. The detailed analysis of the triggers and effects of these bugs shows that most of them can be revealed in low-fidelity simulation. It also provides insights into interesting navigation scenarios to test as well as into how to address the test oracle problem.

show abstract

Reproducibility of Environment-Dependent Software Failures: An Experience Report

Cited by 26 publications

References 16 publications

Analysis of bugs in Google security research project database

Analysis of bugs in Google security research project database

Defect analysis in mission-critical software systems: a detailed investigation

Can Robot Navigation Bugs Be Found in Simulation? An Exploratory Study

Contact Info

Product

Resources

About