activity
20202025
collaborators
Showing cs.SEShow all

6 papers · 1 filter

cs.SE2025

Finding Important Stack Frames in Large Systems

Aleksandr Khvorov, Yaroslav Golubev, Denis Sushentsev

In this work, we developed, integrated, and tested a feature that automatically highlights potentially important frames in stack traces. The feature was implemented in the internal…

cs.SE2024

Stack Trace Deduplication: Faster, More Accurately, and in More Realistic Scenarios

Egor Shibaev, Denis Sushentsev, Yaroslav Golubev +1

In large-scale software systems, there are often no fully-fledged bug reports with human-written descriptions when an error occurs. In this case, developers rely on stack traces, i…

cs.SE2022

Aggregation of Stack Trace Similarities for Crash Report Deduplication

Nikolay Karasov, Aleksandr Khvorov, Roman Vasiliev +2

The automatic collection of stack traces in bug tracking systems is an integral part of many software projects and their maintenance. However, such reports often contain a lot of d…

cs.SE2022

DapStep: Deep Assignee Prediction for Stack Trace Error rePresentation

Denis Sushentsev, Aleksandr Khvorov, Roman Vasiliev +2

The task of finding the best developer to fix a bug is called bug triage. Most of the existing approaches consider the bug triage task as a classification problem, however, classif…

cs.SE2021

S3M: Siamese Stack (Trace) Similarity Measure

Aleksandr Khvorov, Roman Vasiliev, George Chernishev +3

Automatic crash reporting systems have become a de-facto standard in software development. These systems monitor target software, and if a crash occurs they send details to a backe…

cs.SE2020

TraceSim: A Method for Calculating Stack Trace Similarity

Roman Vasiliev, Dmitrij Koznov, George Chernishev +3

Many contemporary software products have subsystems for automatic crash reporting. However, it is well-known that the same bug can produce slightly different reports. To manage thi…