Filters








282,605 Hits in 4.3 sec

Finding and Fixing Faults [chapter]

Stefan Staber, Barbara Jobstmann, Roderick Bloem
2005 Lecture Notes in Computer Science  
We present a method to automatically locate and correct faults in a finite state system, either at the gate level or at the source level.  ...  Knowing that a program has a bug is good, knowing its location is better, but a fix is best.  ...  We furthermore assume that a (partial) specification is given in Linear Temporal Logic (LTL), and we endeavor to find and fix a fault in such a way that the new system satisfies its specification for all  ... 
doi:10.1007/11560548_6 fatcat:xq2iutykkvffxdrhmx37fcwzxy

Finding and fixing faults

Barbara Jobstmann, Stefan Staber, Andreas Griesmayer, Roderick Bloem
2012 Journal of computer and system sciences (Print)  
We present a method to automatically locate and correct faults in a finite state system, either at the gate level or at the source level.  ...  Knowing that a program has a bug is good, knowing its location is better, but a fix is best.  ...  We furthermore assume that a (partial) specification is given in Linear Temporal Logic (LTL), and we endeavor to find and fix a fault in such a way that the new system satisfies its specification for all  ... 
doi:10.1016/j.jcss.2011.05.005 fatcat:xgyk5kna65fcnkavnteppvcasi

You Cannot Fix What You Cannot Find! An Investigation of Fault Localization Bias in Benchmarking Automated Program Repair Systems [article]

Kui Liu and Anil Koyuncu and Tegawendé F. Bissyandé and Dongsun Kim and Jacques Klein and Yves Le Traon
2019 arXiv   pre-print
In this work, we identify and investigate a practical bias caused by the fault localization (FL) step in a repair pipeline.  ...  the number of fixed bugs) is potentially misleading due to the bias of FL configurations; and (c) APR authors do not properly qualify their performance achievement with respect to the different tuning  ...  [69] investigated the influence of the fault space on the success of finding correct patches by the APR tool. The fault space is defined as a ranked list of suspicious entities in a program.  ... 
arXiv:1812.07283v2 fatcat:3sxpr7ofynbxtahkceuf4dfylq

You Cannot Fix What You Cannot Find! An Investigation of Fault Localization Bias in Benchmarking Automated Program Repair Systems

Kui Liu, Anil Koyuncu, Tegawende F. Bissyande, Dongsun Kim, Jacques Klein, Yves Le Traon
2019 2019 12th IEEE Conference on Software Testing, Validation and Verification (ICST)  
In this work, we identify and investigate a practical bias caused by the fault localization (FL) step in a repair pipeline.  ...  the number of fixed bugs) is potentially misleading due to the bias of FL configurations; and (c) APR authors do not properly qualify their performance achievement with respect to the different tuning  ...  ACKNOWLEDGEMENTS This work is supported by the Fonds National de la Recherche (FNR), Luxembourg, under projects RECOM-MEND 15/IS/10449467 and FIXPATTERN C15/IS/9964569.  ... 
doi:10.1109/icst.2019.00020 dblp:conf/icst/LiuKB0KT19 fatcat:qd4t32hobjaefi4bvpxnnogj7q

Software faults in evolving a large, real-time system: a case study [chapter]

Dewayne E. Perry, Carol S. Stieg
1993 Lecture Notes in Computer Science  
Keywords: Software fault analysis; large-scale, real-time system case study; design and coding faults; interface and implementation faults; effort to find/fix faults; underlying causes of faults; means  ...  For the second part, we describe the questionaire used to survey the design and coding faults, report the faults that occurred, how difficult they were to find and to fix, what their underlying causes  ...  (as exemplified by Perry and Wolf [17] and the Inscape Environment [15] ).  ... 
doi:10.1007/3-540-57209-0_5 fatcat:eaqetbjzmfcofkwlhnkb6xdhsa

"Automated Debugging Considered Harmful" Considered Harmful: A User Study Revisiting the Usefulness of Spectra-Based Fault Localization Techniques with Professionals Using Real Bugs from Large Systems

Xin Xia, Lingfeng Bao, David Lo, Shanping Li
2016 2016 IEEE International Conference on Software Maintenance and Evolution (ICSME)  
Our study finds that both the accurate and mediocre spectra-based fault localization tools can help professionals to save their debugging time, and the improvements are statistically significant and substantial  ...  We also discuss implications of our findings to future directions of spectra-based fault localization.  ...  Thus, I change it as "Dim*0.5", and I find that the bug is fixed."  ... 
doi:10.1109/icsme.2016.67 dblp:conf/icsm/XiaBLL16 fatcat:e2s4nqvksretjdcpoc3bgay2ey

An Empirical Study of OSS-Fuzz Bugs [article]

Zhen Yu Ding, Claire Le Goues
2021 arXiv   pre-print
We examine the characteristics of fuzzer-found faults, the lifecycles of such faults, and the evolution of fuzzing campaigns over time.  ...  We find that OSS-Fuzz is often effective at quickly finding bugs, and developers are often quick to patch them.  ...  Any opinions or findings expressed are those of the authors and do not necessarily reflect those of the US Government.  ... 
arXiv:2103.11518v1 fatcat:vlwdeclmx5cflhgts2zpajccjm

Prevalence of Single-Fault Fixes and Its Impact on Fault Localization

Alexandre Perez, Rui Abreu, Marcelo D'Amorim
2017 2017 IEEE International Conference on Software Testing, Verification and Validation (ICST)  
We describe an approach to mine repositories, find bug-fixes, and catalog them according to the number of faults they fix, to assess the prevalence of single-fault fixes.  ...  Moreover, we draw on the practical implications of our findings to influence and set direction for future research.  ...  The experiment entailed mining their code repositories and finding fault-fixing commits following the methodology described in Section IV.  ... 
doi:10.1109/icst.2017.9 dblp:conf/icst/PerezAd17 fatcat:ibuwgnamrncn7fgxndccvb3usi

GLAD: Neural Predicate Synthesis to Repair Omission Faults [article]

Sungmin Kang, Shin Yoo
2022 arXiv   pre-print
Existing template and learning-based APR tools have successfully found patches for many benchmark faults.  ...  Thanks to the shift from translation to synthesis, GLAD is highly orthogonal to existing techniques: GLAD can correctly fix 16 Defects4J v1.2 faults that previous NMT-based techniques could not, while  ...  We find that GLAD is highly orthogonal to existing work, fixing 16 faults never fixed by previous learning-based tools, and fixing eight faults no other tool has fixed.  ... 
arXiv:2204.06771v1 fatcat:vuzwzo762bffpaaar6qlfiepwi

Demystifying Developers' Issues in Distributed Training of Deep Learning Software [article]

Diandian Gu, Zhenpeng Chen, Yuanqiang Liu, Zili Zhang, Yun Ma, Xin Jin, Xuanzhe Liu
2021 arXiv   pre-print
We construct a fine-grained taxonomy consisting of 30 categories regarding the fault symptoms and summarize common fix patterns for different symptoms.  ...  To this end, we extract and analyze 1,054 real-world developers' issues in distributed training from Stack Overflow and GitHub, two commonly used data sources for studying software issues.  ...  Finding 7: We identify six frequent fix patterns for faults in communication setup.  ... 
arXiv:2112.06222v1 fatcat:kmmqsghqgbdu3btozzysmgy664

An Empirical Study on Deployment Faults of Deep Learning Based Mobile Applications [article]

Zhenpeng Chen and Huihan Yao and Yiling Lou and Yanbin Cao and Yuanqiang Liu and Haoyu Wang and Xuanzhe Liu
2021 arXiv   pre-print
Based on the identified faults, we construct a fine-granularity taxonomy consisting of 23 categories regarding to fault symptoms and distill common fix strategies for different fault types.  ...  Deep Learning (DL) is finding its way into a growing number of mobile software applications.  ...  Finding 5: We identify nine frequent fix strategies for faults in model conversion.  ... 
arXiv:2101.04930v2 fatcat:hsy53lqbcreg3dbkpqtocnhjca

A Study of Causes and Consequences of Client-Side JavaScript Bugs

Frolin S. Ocariza, Kartik Bajaj, Karthik Pattabiraman, Ali Mesbah
2017 IEEE Transactions on Software Engineering  
The goal of our study is to understand the root causes and impact of JavaScript faults and how the results can impact JavaScript programmers, testers and tool developers.  ...  While prior studies have demonstrated the prevalence of JavaScript faults, no attempts have been made to determine their causes and consequences.  ...  Triage and Fix Time for JavaScript Faults We calculated the triage time and fix time for each bug report.  ... 
doi:10.1109/tse.2016.2586066 fatcat:ehn4lenkevatvko5jkmb7gug4m

WhoseFault: Automatic developer-to-fault assignment through fault localization

Francisco Servant, James A. Jones
2012 2012 34th International Conference on Software Engineering (ICSE)  
actual developer who fixed the fault.  ...  This paper describes a new technique, which automatically selects the most appropriate developers for fixing the fault represented by a failing test case, and provides a diagnosis of where to look for  ...  We also intend to experiment with applying different techniques in each of the components of our approach -using different line-mapping techniques, fault-localization techniques, and expertise techniquesand  ... 
doi:10.1109/icse.2012.6227208 dblp:conf/icse/ServantJ12 fatcat:zetlj2muzve4vjnmffrqcbrosm

An Empirical Investigation of Predicting Fault Count, Fix Cost and Effort Using Software Metrics

Raed Shatnawi, Wei Li
2016 International Journal of Advanced Computer Science and Applications  
In this study, we present methods and models for the prediction of fault-count, fault-fix cost, and fault-fix effort and compare the effectiveness of different prediction models.  ...  The cost fix models show equal or better performance than fault count and effort models.  ...  Research Questions Given the information available on fault count, fix cost and fix effort, this research aims to find answers for the following research questions.  ... 
doi:10.14569/ijacsa.2016.070264 fatcat:p3zy7j4tyzc3hjursarsmmqgku

Automated fixing of programs with contracts

Yi Wei, Yu Pei, Carlo A. Furia, Lucas S. Silva, Stefan Buchholz, Bertrand Meyer, Andreas Zeller
2010 Proceedings of the 19th international symposium on Software testing and analysis - ISSTA '10  
AutoFix-E 4  Find fixes using  Contracts  Boolean Query Abstraction  Plan:  1) Assess Object State  2) Construct Fault Profile and Behavioral Model  3) Generate Candidate Fixes  4  ...  fixing time: 2.6 minutes  Small study with programmers  4 of 6 proposed valid fixes were same as programmers'  Improve behavior model  Different fault types  Find faults in contracts  Languages without  ... 
doi:10.1145/1831708.1831716 dblp:conf/issta/WeiPFSBMZ10 fatcat:rklwq5dlerhnpf2wbjvuhx3cme
« Previous Showing results 1 — 15 out of 282,605 results