Detecting inaccurate stack traces in bug reports

Simple item page
dc.contributor.authorBheree, Meher K.
dc.contributor.authorUniversity of Lethbridge. Faculty of Arts and Science
dc.contributor.supervisorAnvik, John
dc.date.accessioned2023-03-02T23:04:21Z
dc.date.available2023-03-02T23:04:21Z
dc.date.issued2022
dc.degree.levelMastersen_US
dc.description.abstractThe generally held opinion in the software engineering community is that incorrect information in bug reports is often found in non-structural fields such as bug descriptions and steps to reproduce. However, structural information such as software stack traces can be inaccurate, increasing the project costs due to wasted time in fixed faults. Regarding the occurrence of inaccurate stack traces in bug reports, there is little empirical evidence. Therefore, we seek to provide such evidence by conducting an empirical study on the bug reports containing stack traces from the Eclipse and Apache projects. We propose an approach to classify the stack traces as either “Accurate” or “Inaccurate” by comparing the file names found in a stack trace in a bug report and the corresponding commit history for its fix. Thus, we determine the occurrence of inaccurate stack traces and identify the frequently occurring exception types that appears in the inaccurate stack traces for each project. Finally, we investigate training three supervised machine learning algorithms (Naive Bayes, Support Vector Machines and Logistic Regression), on features extracted from stack traces to create recommender that labels stack traces in bug reports as either ”Accurate” or ”Inaccurate”. The Logistic Regression algorithm was found to perform better with a F1- score up to 87% for the investigated Eclipse projects and 96% for the investigated Apache projects.en_US
dc.identifier.urihttps://hdl.handle.net/10133/6447
dc.language.isoen_US
dc.proquest.subject0984en_US
dc.proquestyesYesen_US
dc.publisherLethbridge, Alta. : University of Lethbridge, Dept. of Mathematics and Computer Science
dc.publisher.departmentDepartment of Mathematics and Computer Scienceen_US
dc.publisher.facultyArts and Scienceen_US
dc.relation.ispartofseriesThesis (University of Lethbridge. Faculty of Arts and Science
dc.subjectStack tracesen_US
dc.subjectBug reportsen_US
dc.subjectBug report qualityen_US
dc.subjectCrash reportsen_US
dc.subjectSoftware debuggingen_US
dc.subjectInaccurate informationen_US
dc.subjectExceptionsen_US
dc.subjectRecommender creationen_US
dc.subject.lcshMachine learning
dc.subject.lcshDebugging in computer science
dc.subject.lcshSoftware failure
dc.subject.lcshDissertations, Academic
dc.titleDetecting inaccurate stack traces in bug reportsen_US
dc.typeThesisen_US
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
BHEREE_MEHER_MSC_2022.pdf
Size:
2.53 MB
Format:
Adobe Portable Document Format
Description:
Download
License bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
license.txt
Size:
3.25 KB
Format:
Item-specific license agreed upon to submission
Description:
Download
Collections
Arts and Science, Faculty of
University of Lethbridge Theses