Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Sigmund Chianasta

dblp:299/1769 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2023
0000-0001-7475-0881ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Program analysis · 56% Debugging and program repair · 28% Concurrent programming · 17%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Debugging and program repair
automated program repair
0.712023
Hippodrome: Data Race Repair Using Static Analysis Summaries · ACM Trans. Softw. Eng. Methodol. 2023
Program analysis › static analysis › modular analysis
compositional static analysis
0.712023
Hippodrome: Data Race Repair Using Static Analysis Summaries · ACM Trans. Softw. Eng. Methodol. 2023
Program analysis
static analysis
0.712023
Hippodrome: Data Race Repair Using Static Analysis Summaries · ACM Trans. Softw. Eng. Methodol. 2023
Concurrent programming
concurrency bugs
0.212023
Hippodrome: Data Race Repair Using Static Analysis Summaries · ACM Trans. Softw. Eng. Methodol. 2023
Concurrent programming › concurrency bugs
data races
0.212023
Hippodrome: Data Race Repair Using Static Analysis Summaries · ACM Trans. Softw. Eng. Methodol. 2023

Methods — techniques the papers use, named apart from their topics

static analysis summaries · 0.7compositional analysis · 0.7
YearPublicationVenuePosition
2023 Hippodrome: Data Race Repair Using Static Analysis Summaries
abstract
Implementing bug-free concurrent programs is a challenging task in modern software development. State-of-the-art static analyses find hundreds of concurrency bugs in production code, scaling to large codebases. Yet, fixing these bugs in constantly changing codebases represents a daunting effort for programmers, particularly because a fix in the concurrent code can introduce other bugs in a subtle way. In this work, we show how to harness compositional static analysis for concurrency bug detection, to enable a new Automated Program Repair (APR) technique for data races in large concurrent Java codebases. The key innovation of our work is an algorithm that translates procedure summaries inferred by the analysis tool for the purpose of bug reporting into small local patches that fix concurrency bugs (without introducing new ones). This synergy makes it possible to extend the virtues of compositional static concurrency analysis to APR, making our approacheffective(it can detect and fix many more bugs than existing tools for data race repair),scalable(it takes seconds to analyze and suggest fixes for sizeable codebases), andusable(generally, it does not require annotations from the users and can performcontinuousautomated repair). Our study, conducted on popular open-source projects, has confirmed that our tool automatically produces concurrency fixes similar to those proposed by the developers in the past.
Andreea Costea, Abhishek Tiwari 0001, Sigmund Chianasta, Kishore R, Abhik Roychoudhury, Ilya Sergey
ACM Trans. Softw. Eng. Methodol.3