1/2/2024 0 Comments Mucommander text overlapping![]() ![]() We divided the bugs into production- and test-related bugs. These problems arise from using different bug types without clearly distinguishing them. They are in both the ground truth and the search space. To this end, we surveyed 50 previous studies, collected 41,754 bug reports, and found out critical problems that affect the validity of results of performance evaluation. To accurately evaluate the IRBL and furthermore improve the performance, it is strongly required to analyze the validity of these datasets in advance. Various evaluation datasets are used to evaluate the performance of information retrieval-based bug localization (IRBL) techniques. 2014) commonly used to evaluate the IRBL performance, as well as one recently released dataset. 2019), and collected five representative datasets (Zhou et al. 2013 Sisman and Kak 2013 Davies and Roper 2013 Tantithamthavorn et al. We surveyed 50 recent studies over the last seven years (Zhou et al. In short, our findings highlight possible future research directions to better help practitioners attach or analyze logs in bug reports. In addition, some logging statements are removed in the source code as the system evolves, which may cause further challenges in analyzing the logs. In fact, through call graph analysis, we find that 28% of the studied bug reports have the fixed classes reachable from the logged classes, while they are not visible in the logs attached in bug reports. Many logs only show the point of failure (e.g., exception) and do not provide a direct hint on the actual root cause. 3) Our manual study finds that there is often missing system execution information in the logs. However, there is still a large number of bug reports where there is no overlap between the logged and fixed classes. Most bug reports (73%) have overlaps between the classes that generate the logs and their corresponding fixed classes. 2) Logs often provide a good indication of where a bug is located. We also find that reporters may not attach accurate or sufficient logs (i.e., developers often ask for additional logs in the Comments section of a bug report), which extends the bug resolution time. Our findings show that: 1) BRWL takes longer time (median ranges from 3 to 91 days) to resolve compared to BRNL (median ranges from 1 to 25 days). We conduct our study on 10 large-scale open-source systems with a total of 1,561 bug reports with logs (BRWL) and 7,287 bug reports without logs (BRNL). In particular, we study both log snippets and exception stack traces in bug reports. In this paper, we conduct an empirical study on the challenges that developers may encounter when analyzing the user-provided logs and their benefits. However, some logs may be incomplete or inaccurate, which can cause difficulty for developers to diagnose the bug, and thus, delay the bug fixing process. Intuitively, user-provided logs illustrate the problems that users encounter and may help developers with the debugging process. During the debugging process, developers need to study the bug report and examine user-provided logs to understand the system executions that lead to the problem. ![]() Logs in bug reports provide important debugging information for developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |