gousiosg / java-stacktrace-analysis Goto Github PK

Hi all,

The present title is

What can Issues on GitHub and Google Code tell us about Bug Hazards in Android and Java?

Should not exceptions (and possibly stack traces) be part of the title?

I'm also not 100% sure the title should be a question.

A more accurate title to me would be:

An Analysis of Exception Handling Bug Hazards in Android and Java based on GitHub and Google Code Issues

Or, alternatively,

An Analysis of Exception Handling Bug Hazards in Android and Java based on Reported Stack Traces

We don't expect that the results will be different if we'd analyze bitbucket, jira, or sourceforge, so the fact that we analyze github / google code is perhaps less relevant for the title.

The paper presently states that byte code analysis is conducted, but it is left very implicit where this byte code actually comes from.

I think section III should make very clear where that byte code comes from. Do you actually compile code to obtain the byte code? Or do you analyze given jars?

What about versioning? How do you know which version of the byte code you should analyze for a given issue?