Orion+: Automated Problem Diagnosis in Computing Systems by Mining Metric Data

02/28/2018
by   Shreya Inamdar, et al.
0

This work presents the suspicious code at a finer granularity of call stack rather than code region, which was being returned by Orion. Call stack based comparison returns call stacks that are most impacted by the bug and save developer time to debug from scratch. This solution has polynomial complexity and hence can be implemented practically.

READ FULL TEXT
POST COMMENT

Comments

There are no comments yet.

Authors

page 22

page 23

page 24

page 26

04/17/2020

An Annotated Dataset of Stack Overflow Post Edits

To improve software engineering, software repositories have been mined f...
06/21/2018

Awareness and Experience of Developers to Outdated and License-Violating Code on Stack Overflow: An Online Survey

We performed two online surveys of Stack Overflow answerers and visitors...
01/14/2022

DapStep: Deep Assignee Prediction for Stack Trace Error rePresentation

The task of finding the best developer to fix a bug is called bug triage...
04/17/2020

Can We Use Stack Overflow as a Source of Explainable Bug-fix Data?

Bug-fix data sets are important for building various software engineerin...
03/18/2021

S3M: Siamese Stack (Trace) Similarity Measure

Automatic crash reporting systems have become a de-facto standard in sof...
08/17/2021

Solving the Funarg Problem with Static Types

The difficulty associated with storing closures in a stack-based environ...
04/30/2022

Aggregation of Stack Trace Similarities for Crash Report Deduplication

The automatic collection of stack traces in bug tracking systems is an i...
This week in AI

Get the week's most popular data science and artificial intelligence research sent straight to your inbox every Saturday.