{'fraction_non_alphanumeric': 0.016291698991466253, 'fraction_numerical': 0.0, 'mean_word_length': 5.417910447761194, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Bug Localization Approach Based on Similar Bug Report, Stack Trace and Source Code Structure

Bug localization helps software developers to track post-released faulty source files with the help of user’s reported bug files. Bug localization gains high popularity in software maintenance since many recent years due to its essential role to fix unavoidable bugs encountered in software development process. In this paper, we propose bug localization approach for locating erroneous faulty source files. It recommends relevant faulty source files to fix according to their highest similarity scores. We additionally exploit information retrieval techniques to consider the source and bug files as documents so that we can retrieve the similar terms from the code structures with different levels, historical bug documents and stack-trace information of both of files. We implement the proposed system on the top of BugLocator equipped with our methods and contributions. We then perform the experiments and compare the results with proficient contemporary approaches: BugLocator and BLUiR in terms of top-N rank, mean average precision (MAP) and mean reciprocal rank (MRR) evaluation metrics. The results show that the proposed system achieves more significant results than other approaches.