Filters








9,865 Hits in 5.7 sec

Do stack traces help developers fix bugs?

Adrian Schroter, Adrian Schröter, Nicolas Bettenburg, Rahul Premraj
2010 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)  
Our results provide strong evidence to this effect and also throws light on some of the patterns in bug fixing using stack traces.  ...  We expect the findings of our study to further emphasize the importance of adding stack traces to bug reports and that in the future, software vendors will provide more support in their products to help  ...  RQ4: Do stack traces help speed up debugging?  ... 
doi:10.1109/msr.2010.5463280 dblp:conf/msr/SchroterBP10 fatcat:ilrmyqwckrdx5l3kdxieezwz5m

Improving bug tracking systems

Thomas Zimmermann, Rahul Premraj, Jonathan Sillito, Silvia Breu
2009 2009 31st International Conference on Software Engineering - Companion Volume  
It is important that information provided in bug reports is relevant and complete in order to help resolve bugs quickly.  ...  As a proof-of-concept, we also demonstrate a prototype interactive bug tracking system that gathers relevant information from the user and identifies files that need to be fixed to resolve the bug.  ...  For example, bug tracking systems can be configured to automatically locate the relevant stack trace and add it to a bug report.  ... 
doi:10.1109/icse-companion.2009.5070993 dblp:conf/icse/ZimmermannPSB09 fatcat:ka3sngw4yrdkrptbubo77sajvi

The significance of bug report elements

Mozhan Soltani, Felienne Hermans, Thomas Bäck
2020 Empirical Software Engineering  
The results show developers find it highly important that bug reports include crash description, reproducing steps or test cases, and stack traces.  ...  Statistical analysis on the mined issues shows that crash reproducing steps, stack traces, fix suggestions, and user contents, have statistically significant impact on bug resolution times, for ∼70%, ∼  ...  What Types of Information do Developers Perceive as Important in Bug Reports?  ... 
doi:10.1007/s10664-020-09882-z fatcat:7skg4fhy2nczheats6zl44ohzu

What's in a bug report?

Steven Davies, Marc Roper
2014 Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM '14  
Those sources deemed highly useful by developers and tools such as stack traces and test cases appeared very infrequently.  ...  the system, but also as the basis of automated tools to assist in the challenging tasks of finding and fixing bugs.  ...  For example, we do not know how many bugs without Stack traces did not generate a stack trace, and how many did generate a stack trace but the user chose not to report it.  ... 
doi:10.1145/2652524.2652541 dblp:conf/esem/DaviesR14 fatcat:kqduakucdzfsbdtgulpwnxmcjm

Exception handling bug hazards in Android

Roberta Coelho, Lucas Almeida, Georgios Gousios, Arie van Deursen, Christoph Treude
2016 Empirical Software Engineering  
The results corroborate the stack trace findings, and indicate that developers are unaware of frequently occurring undocumented exception handling behavior.  ...  The goal of this paper is to obtain a thorough understanding of common exception handling bug hazards that app developers face.  ...  [48] conducted an empirical study on the usefulness of stack traces for bug fixing and showed that developers fixed the bugs faster when failing stack traces were included in bug issues.  ... 
doi:10.1007/s10664-016-9443-7 fatcat:ypqsntbasngw7lqmvzubiixcdi

Improving bug triage with bug tossing graphs

Gaeul Jeong, Sunghun Kim, Thomas Zimmermann
2009 Proceedings of the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering on European software engineering conference and foundations of software engineering symposium - ESEC/FSE '09  
A bug report is typically assigned to a single developer who is then responsible for fixing the bug.  ...  First, it reveals developer networks which can be used to discover team structures and to find suitable experts for a new task. Second, it helps to better assign developers to bug reports.  ...  For example, bug reports that are easy to read or bug reports with several attachments, stack traces, or code samples are fixed sooner.  ... 
doi:10.1145/1595696.1595715 dblp:conf/sigsoft/JeongKZ09 fatcat:azjyx5lhjnhplpuaxucdzrjqc4

Quality of bug reports in Eclipse

Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiß, Rahul Premraj, Thomas Zimmermann
2007 Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange - eclipse '07  
Our results show that steps to reproduce and stack traces are most sought after by developers, while inaccurate steps to reproduce and incomplete information pose the largest hurdles.  ...  Surprisingly, developers are indifferent to bug duplicates. Such insight is useful to design new bug tracking tools that guide reporters at providing more helpful information.  ...  A special thanks to all ECLIPSE developers who responded to our survey.  ... 
doi:10.1145/1328279.1328284 dblp:conf/eclipse/BettenburgJSWPZ07 fatcat:4rsl5a5w3ngkply2kqqmx7ziqy

Improving bug management using correlations in crash reports

Shaohua Wang, Foutse Khomh, Ying Zou
2014 Empirical Software Engineering  
Through an empirical study on Firefox and Eclipse, we show that the first three rules can identify crash correlation groups using stack trace information, with a precision of 91% and a recall of 87% for  ...  Usually, developers prioritize crash types based on the number of crash reports and file bug reports for the top crash types.  ...  Acknowledgements The authors would like to thank Tejinder Dhaliwal and Feng Zhang, of Queen's University, for their help during data collection and for their many useful comments on this work.  ... 
doi:10.1007/s10664-014-9333-9 fatcat:irla6shb6ncsfgavmlqbilszn4

Improving bug localization using correlations in crash reports

Shaohua Wang, Foutse Khomh, Ying Zou
2013 2013 10th Working Conference on Mining Software Repositories (MSR)  
Developers can combine the proposed crash correlation rules with the new bug localization algorithm to identify and fix correlated crash types all together.  ...  Usually, developers prioritize crash types based on the number of crash reports and file bugs for the top crash types.  ...  ACKNOWLEDGMENT The authors would like to thank Tejinder Dhaliwal and Feng Zhang, of Queen's University, for his help during data collection and for his many useful comments on this work.  ... 
doi:10.1109/msr.2013.6624036 dblp:conf/msr/WangKZ13 fatcat:b656i4r4hjer3lzbnz665egqqe

Extracting structural information from bug reports

Nicolas Bettenburg, Rahul Premraj, Thomas Zimmermann, Sunghun Kim
2008 Proceedings of the 2008 international workshop on Mining software repositories - MSR '08  
In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches.  ...  In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them.  ...  Developers can use it to find specific information related to bug reports, such as "Find me all patches and stack traces related to Bug # 12345."  ... 
doi:10.1145/1370750.1370757 dblp:conf/msr/BettenburgPZK08 fatcat:xjplzvmvmfavla6hbighp2ybte

Effective Bug Tracking Systems: Theories and Implementation

Akhilesh Babu Kolluri
2012 IOSR Journal of Computer Engineering  
To demonstrate the efficiency of the proposed directions, we develop a prototype application that tracks bugs effectively by capturing essential information from users and help resolve bugs quickly.  ...  The bulk of information provided in the bug reports may cause problem to developers in ascertaining poorly designed information.  ...  Tool oriented does mean that the bug tracking systems can be configured to collect stack trace implicitly and add it to the report that contains bug details.  ... 
doi:10.9790/0661-0463136 fatcat:42ebltiw4zhxdmbikksmdjbvbi

Reusing debugging knowledge via trace-based bug search

Zhongxian Gu, Earl T. Barr, Drew Schleck, Zhendong Su
2012 SIGPLAN notices  
A fix for a similar bug can help a developer understand a bug, or even directly fix it. Studying bugs with similar symptoms, programmers may determine how to detect or resolve them.  ...  OSCILLOSCOPE displays the traces of the bugs it returns against the trace of the target bug, so a developer can visually examine the quality of the matches.  ...  In this section, we show how OSCILLOSCOPE can help a programmer fix a bug by identifying bugs similar to that bug. To do so, we issue a suffix query for each bug.  ... 
doi:10.1145/2398857.2384684 fatcat:gewao56n5vc7hgur2aoqkekema

Reusing debugging knowledge via trace-based bug search

Zhongxian Gu, Earl T. Barr, Drew Schleck, Zhendong Su
2012 Proceedings of the ACM international conference on Object oriented programming systems languages and applications - OOPSLA '12  
A fix for a similar bug can help a developer understand a bug, or even directly fix it. Studying bugs with similar symptoms, programmers may determine how to detect or resolve them.  ...  OSCILLOSCOPE displays the traces of the bugs it returns against the trace of the target bug, so a developer can visually examine the quality of the matches.  ...  In this section, we show how OSCILLOSCOPE can help a programmer fix a bug by identifying bugs similar to that bug. To do so, we issue a suffix query for each bug.  ... 
doi:10.1145/2384616.2384684 dblp:conf/oopsla/GuBSS12 fatcat:24twha4f4jhtxec4j52lkpsx44

A qualitative study on performance bugs

S. Zaman, B. Adams, A. E. Hassan
2012 2012 9th IEEE Working Conference on Mining Software Repositories (MSR)  
However, in earlier work we found that performance bugs take more time to fix, need to be fixed by more experienced developers and require changes to more code than non-performance bugs.  ...  We found that developers and users face problems in reproducing performance bugs and have to spend more time discussing performance bugs than other kinds of bugs.  ...  Both developers and reporters accepted that 'steps to reproduce' in bug reports are the most helpful information. Test cases and stack traces were next in the list.  ... 
doi:10.1109/msr.2012.6224281 dblp:conf/msr/ZamanAH12 fatcat:z3lpd2x2arehxao2ld63yw6lq4

Automated Concurrency-Bug Fixing

Guoliang Jin, Wei Zhang, Dongdong Deng
2012 USENIX Symposium on Operating Systems Design and Implementation  
CFix also simplifies its own patches by merging fixes for related bugs.  ...  Concurrency bugs are widespread in multithreaded programs. Fixing them is time-consuming and error-prone. We present CFix, a system that automates the repair of concurrency bugs.  ...  We thank the Opera group from UCSD for sharing with us their bug benchmarks.  ... 
dblp:conf/osdi/Jin0D12 fatcat:ceag7emuijatjprvg2idsi4emi
« Previous Showing results 1 — 15 out of 9,865 results