Anatomy of a crash repository
نویسندگان
چکیده
4 This work investigates the properties of crash reports collected from Ubuntu Linux users. Understanding crash reports is important to better store, categorize, prioritize, parse, triage, assign bugs to, and potentially synthesize them. Understanding what is in a crash report, and how the metadata and stack traces in crash reports vary will help solve, debug, and prevent the causes of crashes. 10 different aspects of 40,592 crash reports about 1,921 pieces of software submitted by users and developers to the Ubuntu project were analyzed, plotted, and statistical distributions were fitted to some of them. We investigated the structure and properties of crash reports. Crashes have many properties that seem to have distributions similar to standard statistical distributions, but with even longer tails than expected. These aspects of crash reports have not been analyzed statistically before. We found that many applications only had a single crash, while a few applications had a large number of crashes reported. Crash bucket size (clusters of similar crashes) also followed a Zipf-like distribution. The lifespan of buckets ranged from less than an hour to over four years. Some stack traces were short, and some were so long they were truncated by the tool that produced them. Many crash reports had no recursion, some contained recursion, and some displayed evidence of unbounded recursion. Linguistics literature hinted that sentence length follows a gamma distribution; this is not the case for function name length. Additionally, only two hardware architectures, and a few signals are reported for almost all of the crashes in the Ubuntu dataset. Many crashes were similar but there were also many unique crashes. This study of crashes from 1,921 projects will be valuable for anyone who wishes to: cluster or deduplicate crash reports, synthesize or simulate crash reports, store or triage crash reports, or data-mine crash reports. 5
منابع مشابه
The Unreasonable Effectiveness of 1 Traditional Information Retrieval in Crash
6 Organizations like Mozilla, Microsoft, and Apple are flooded with thousands of automated crash reports per day. Although crash reports contain valuable information for debugging, there are often too many for developers to examine individually. Therefore, in industry, crash reports are often automatically grouped together in buckets. Ubuntu’s repository contains crashes from hundreds of softwa...
متن کاملAn Investigation on Crash Worthiness of Different Vehicle Brands: A Case Study of Rollover Crashes
This study aimed at indexing crash worthiness capability of 20 most frequently used car brands in Iran. Since rollover crashes are one of the most important crash types due to their high impact on crash severity, they were chosen as the case study of the current research. In this regard, the data of 42,118 rollover crashes of urban and rural roads of Iran which occurred from 2009 to 2012 was us...
متن کاملCrash Injury Analysis of Knee Joint Considering Pedestrian Safety
Background: Lower extremity injuries are frequently observed in car-to-pedestrian accidents and due to the bumper height of most cars, knee joint is one of the most damaged body parts in car-to-pedestrian collisions.Objective: The aim of this paper is first to provide an accurate Finite Element model of the knee joint and second to investigate lower limb impact biomechanics in car-to-pede...
متن کاملForecasting Crash risk using Business Strategy, Equity Overvaluation and Conditional Skewness in Stock Price
A firm is called to have stock price crash risk if the firm has a tendency to experience a sudden drop in its stock price. In this study, the relation between the firm-level of business strategy and future stock price crash risk Is examined, as well as the effect of stock overvaluation on the relationship between business strategy and crash risk investigated. Using the strategy index and crash ...
متن کاملPackage Management Security
Package management is the task of determining which packages should be installed on a host and then downloading and installing those packages. This paper examines the popular package managers APT and YUM and presents nine feasible attacks on them. There are attacks that install malicious packages, deny users package updates, or cause the host to crash. This work identifies three rules of packag...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید
ثبت ناماگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید
ورودعنوان ژورنال:
- PeerJ PrePrints
دوره 4 شماره
صفحات -
تاریخ انتشار 2016