207 Hits in 4.1 sec

Identifying static analysis techniques for finding non-fix hunks in fix revisions

Yungbum Jung, Hakjoo Oh, Kwangkeun Yi
2009 Proceeding of the ACM first international workshop on Data-intensive software management and mining - DSMM '09  
We classified these non-fix hunks into 11 patterns. For all patterns we enumerate enabling static analysis techniques.  ...  Mining software repositories for bug detection requires accurate techniques of identifying bug-fix revisions. There have been many researches to find exact bug-fix revisions.  ...  ACKNOWLEDGMENT We thank Sunghun Kim for his contributions to give us bug-fix revision, their hunks, and many useful comments. We also thank Soonho Kong for his precious comments.  ... 
doi:10.1145/1651309.1651313 dblp:conf/cikm/JungOY09 fatcat:c5d6vfuoavbmhcgblonclf2vam

Towards a better understanding of testing if conditionals [article]

Shimul Kumar Nath, Robert Merkel, Man Fai Lau, Tanay Kanti Paul
2012 arXiv   pre-print
Fault based testing is a technique in which test cases are chosen to reveal certain classes of faults.  ...  identified fault classes.  ...  Among six identified non-fix IF-CC hunks (See in Section III-B), NF-EOEM, NF-EOIE, and NF-ARMP are eliminated as they are detected with static analysis.  ... 
arXiv:1205.6594v1 fatcat:admen3osavethk4shkyxtqap2i

Memories of bug fixes

Sunghun Kim, Kai Pan, E. E. James Whitehead
2006 Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering - SIGSOFT '06/FSE-14  
Analysis of five open source projects shows that, for these projects, 19.3%-40.3% of bugs appear repeatedly in the memories, and 7.9%-15.5% of bug and fix pairs are found in memories.  ...  Furthermore, for the bug and fix pairs, it is possible to both detect the bug and provide a strong suggestion for the fix.  ...  We especially thank Kevin Greenan and the Storage Systems Research Center at UCSC for allowing the use of their cluster for our research.  ... 
doi:10.1145/1181775.1181781 dblp:conf/sigsoft/KimPW06 fatcat:xmeeb4tzqneizhlcswzh3jloq4

Understanding bug fix patterns in verilog

Sangeetha Sudakrishnan, Janaki Madhavan, E. James Whitehead, Jose Renau
2008 Proceedings of the 2008 international workshop on Mining software repositories - MSR '08  
We find that 29 − 55% of the bug fix pattern instances in Verilog involve assignment statements, while 18 − 25% are related to if statements.  ...  In this project, we analyze the bug fix history of four hardware projects written in Verilog and manually define 25 bug fix patterns. The frequency of each bug type is then computed for all projects.  ...  RELATED WORK Bugs in software are difficult to find and costly to fix. Therefore, static code analysis to detect bugs is a very active area of research in software engineering.  ... 
doi:10.1145/1370750.1370761 dblp:conf/msr/SudakrishnanMWR08 fatcat:mxch6ukxufggncpqu5hxd2djzi

DevReplay: Automatic Repair with Editable Fix Pattern [article]

Yuki Ueda, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto
2020 arXiv   pre-print
Static analysis tools, or linters, detect violation of source code conventions to maintain project readability.  ...  Using DevReplay, developers can automatically detect and fix project/API-specific problems in the code editor and code review.  ...  Change distilling techniques are believed to improve the programming language and static analysis tools.  ... 
arXiv:2005.11040v1 fatcat:apz76pygcnanrgdspro47udglu

Toward an understanding of bug fix patterns

Kai Pan, Sunghun Kim, E. James Whitehead
2008 Empirical Software Engineering  
Defined bug fix patterns cover 45.7% to 63.3% of the total bug fix hunk pairs in these projects. The frequency of occurrence of each bug fix pattern is computed across all projects.  ...  Analysis of if conditional bug fix sub-patterns shows a trend towards increasing conditional complexity in if conditional fixes.  ...  Combining static or dynamic analysis and mining repositories techniques to identify bugs are proposed. Williams and Hollingsworth (2005) use project histories to improve existing bug finding tools.  ... 
doi:10.1007/s10664-008-9077-5 fatcat:lxrt5vco6vbotfjztkac5lvhmy

Automatic Identification of Bug-Introducing Changes

Sunghun Kim, Thomas Zimmermann, Kai Pan, E. Jr. Whitehead
2006 21st IEEE/ACM International Conference on Automated Software Engineering (ASE'06)  
Bug-fixes are widely used for predicting bugs or finding risky parts of software. However, a bug-fix does not contain information about the change that initially introduced a bug.  ...  In this paper, we present algorithms to automatically and accurately identify bug-introducing changes.  ...  To check how many bug-fix hunks are true bug-fixes, we manually verified all bug-fix hunks and marked them as bug-fix or non-bug-fix.  ... 
doi:10.1109/ase.2006.23 dblp:conf/kbse/KimZPW06 fatcat:t2h7iqk7rjal3l6u2kskpuo3we

Mining Fix Patterns for FindBugs Violations [article]

Kui Liu, Dongsun Kim, Tegawendé F. Bissyandé, Shin Yoo, Yves Le Traon
2018 arXiv   pre-print
In this paper, we first collect and track a large number of fixed and unfixed violations across revisions of software.  ...  To automatically identify patterns in violations and their fixes, we propose an approach that utilizes convolutional neural networks to learn features and clustering to regroup similar instances.  ...  Static analysis techniques are widely used in modern software projects 32 .  ... 
arXiv:1712.03201v2 fatcat:r37uhraprbhlbgqyyc4nwam7zu

Covrig: a framework for the analysis of code, test, and coverage evolution in real software

Paul Marinescu, Petr Hosek, Cristian Cadar
2014 Proceedings of the 2014 International Symposium on Software Testing and Analysis - ISSTA 2014  
In this paper, we present Covrig, a flexible infrastructure that can be used to run each version of a system in isolation and collect static and dynamic software metrics, using a lightweight virtual machine  ...  patches, analyse the evolution of program and patch coverage, assess the impact of nondeterminism on the execution of test suites, and investigate whether the coverage of code containing bugs and bug fixes  ...  ACKNOWLEDGEMENTS We thank our anonymous reviewers for their constructive comments, and Oscar Soria Dustmann and Hristina Palikareva for their careful proofreading of the text.  ... 
doi:10.1145/2610384.2610419 dblp:conf/issta/MarinescuHC14 fatcat:pabsfaoydbg4jbrt6as7msiwf4

Ownership, experience and defects

Foyzur Rahman, Premkumar Devanbu
2011 Proceeding of the 33rd international conference on Software engineering - ICSE '11  
We find that implicated code is more strongly associated with a single developer's contribution; our findings also indicate that an author's specialized experience in the target file is more important  ...  Using version history, we examine contributions to code fragments that are actually repaired to fix bugs. Are these code fragments "implicated" in bugs the result of contributions from many?  ...  Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the National Science Foundation.  ... 
doi:10.1145/1985793.1985860 dblp:conf/icse/RahmanD11 fatcat:2hitptprszbglg36jnt46iqnii

A Closer Look at Real-World Patches

Kui Liu, Dongsun Kim, Anil Koyuncu, Li Li, Tegawende F. Bissyande, Yves Le Traon
2018 2018 IEEE International Conference on Software Maintenance and Evolution (ICSME)  
We find that there are opportunities for APR techniques to improve their effectiveness by looking at code elements that have not yet been investigated.  ...  For example, a small number of statement and expression types are recurrently impacted by real-world patches, and expression-level granularity could reduce search space of finding fix ingredients, where  ...  [24] further reported that most bug fix hunks (91-96%) are small ones and ignoring large hunks has minimal impact on patch analysis. C.  ... 
doi:10.1109/icsme.2018.00037 dblp:conf/icsm/Liu0K0BT18 fatcat:che3ktarqvdx7j76ze6rsq5bha

Localization of real world regression Bugs using single execution [article]

Dekel Cohen, Amiram Yehudai
2015 arXiv   pre-print
Code changes, such as bug fixes or new feature work, may result in a regression bug.  ...  In over 90% of the cases, the developer only has to examine 10-20 lines of code in order to locate the bug, regardless of the code base size.  ...  Other mitigations, such as Code Reviews, Change classification [5] and Change Impact Analysis using dynamic and static techniques [6] , [7] were also studied.  ... 
arXiv:1505.01286v1 fatcat:lkimxbwcw5cplmsxmp26frd7oy

Shadow Symbolic Execution for Testing Software Patches

Tomasz Kuchta, Hristina Palikareva, Cristian Cadar
2018 ACM Transactions on Software Engineering and Methodology  
Kuchta et al. being achieved in practice [28] , automatic techniques for enabling high-coverage patch testing are becoming more and more successful [1, 24, 27, 40, 43] .  ...  Many of these techniques are based on dynamic symbolic execution [8], a program analysis technique that provides the ability to generate inputs that form high-coverage test suites.  ...  , Martin Nowack, Alessandro Orso, and the anonymous reviewers for their feedback on the work.  ... 
doi:10.1145/3208952 fatcat:xvf77dd3y5ctzb6tngiobzcyue

History-driven Fix for Code Quality Issues

Jiangtao Xue, Xinjun Mao, Yao Lu, Yue Yu, Shangwen Wang
2019 IEEE Access  
To ensure the internal code quality of contributions in open source software (OSS) communities, static analysis tools (e.g.  ...  Evaluated by fixing the unfix CQI Instances, we find that the average correctness of our approach is 80% in top 1 fix patch and 69.17% of Top 5.  ...  ACKNOWLEDGMENT The authors would like to thank developers for participating our live study in GitHub.  ... 
doi:10.1109/access.2019.2934975 fatcat:44lpo6onzjhfrl2fh6umdr5x2i

Shadow of a doubt

Hristina Palikareva, Tomasz Kuchta, Cristian Cadar
2016 Proceedings of the 38th International Conference on Software Engineering - ICSE '16  
The technique works by executing both the old and the new version in the same symbolic execution instance, with the old version shadowing the new one.  ...  In this paper, we present a symbolic execution-based technique that is designed to generate test inputs that cover the new program behaviours introduced by a patch.  ...  26] ; our analysis could potentially provide further information to guide these techniques.  ... 
doi:10.1145/2884781.2884845 dblp:conf/icse/PalikarevaKC16 fatcat:3q4bymlccjhlvimo445btxeccq
« Previous Showing results 1 — 15 out of 207 results