Anchor: Locating Android Framework-specific Crashing Faults
This addresses a debugging challenge for Android developers, offering a novel solution for crashes not covered by traditional methods, though it is incremental in improving localization for a specific domain.
The paper tackles the problem of debugging Android framework-specific app crashes, where buggy code may not appear in stack traces, and proposes Anchor, a lightweight tool that locates crash-inducing bugs outside the stack trace using only crash messages and APK files, achieving effectiveness in experimental evaluations.
Android framework-specific app crashes are hard to debug. Indeed, the callback-based event-driven mechanism of Android challenges crash localization techniques that are developed for traditional Java programs. The key challenge stems from the fact that the buggy code location may not even be listed within the stack trace. For example, our empirical study on 500 framework-specific crashes from an open benchmark has revealed that 37 percent of the crash types are related to bugs that are outside the stack traces. Moreover, Android programs are a mixture of code and extra-code artifacts such as the Manifest file. The fact that any artifact can lead to failures in the app execution creates the need to position the localization target beyond the code realm. In this paper, we propose Anchor, a two-phase suspicious bug location suggestion tool. Anchor specializes in finding crash-inducing bugs outside the stack trace. Anchor is lightweight and source code independent since it only requires the crash message and the apk file to locate the fault. Experimental results, collected via cross-validation and in-the-wild dataset evaluation, show that Anchor is effective in locating Android framework-specific crashing faults.