@conference {Guo:2014:ODC:2597073.2597094,
	title = {Oops! Where Did That Code Snippet Come from?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {52{\textendash}61},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A kernel oops is an error report that logs the status of the Linux kernel at the time of a crash. Such a report can provide valuable first-hand information for a Linux kernel maintainer to conduct postmortem debugging. Recently, a repository has been created that systematically collects kernel oopses from Linux users. However, debugging based on only the information in a kernel oops is difficult. We consider the initial problem of finding the offending line, i.e., the line of source code that incurs the crash. For this, we propose a novel algorithm based on approximate sequence matching, as used in bioinformatics, to automatically pinpoint the offending line based on information about nearby machine-code instructions, as found in a kernel oops. Our algorithm achieves 92\% accuracy compared to 26\% for the traditional approach of using only the oops instruction pointer.},
	keywords = {debugging, linux kernel, oops, sequence alignment},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597094},
	url = {http://doi.acm.org/10.1145/2597073.2597094},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guo.pdf},
	author = {Guo, Lisong and Lawall, Julia and Muller, Gilles}
}
