English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Software crashes due to its increasing complexity. Once a crash happens, acrash report could be sent to software developers for investigation upon userpermission. Because of the large number of crash reports and limitedinformation, debugging for crashes is often a tedious and labor-intensive task.In this paper, we propose a statistical fault localization framework to helpdevelopers locate functions that contain crashing faults. We generate theexecution traces for the failing traces based on the crash stack, and thepassing traces from normal executions. We form program spectra by combininggenerated passing and failing trace, and then apply statistical faultlocalization techniques such as Ochiai to locate the crashing faults. We alsopropose two heuristics to improve the fault localization performance. Weevaluate our approach using the real-world Firefox crash report data. Theresults show that the performance of our method is promising. Our approachpermits developers to locate 63.9% crashing faults by examining only 5% Firefox3.6 functions in the spectra.

Locating Crashing Faults based on Crash Stack Traces