19 citations · 50 across the 14 of their papers we have counts for
14 papers · 1 filter
The Devil Is in the Command Line: Associating the Compiler Flags With the Binary and Build Metadata
Gunnar Kudrjavets, Aditya Kumar, Jeff Thomas +1
Engineers build large software systems for multiple architectures, operating systems, and configurations. A set of inconsistent or missing compiler flags generates code that catast…
What Do You Mean by Memory? When Engineers Are Lost in the Maze of Complexity
Gunnar Kudrjavets, Aditya Kumar, Jeff Thomas +1
An accepted practice to decrease applications' memory usage is to reduce the amount and frequency of memory allocations. Factors such as (a) the prevalence of out-of-memory (OOM) k…
Does Code Review Speed Matter for Practitioners?
Gunnar Kudrjavets, Ayushi Rastogi
Increasing code velocity is a common goal for a variety of software projects. The efficiency of the code review process significantly impacts how fast the code gets merged into the…
Are We Speeding Up or Slowing Down? On Temporal Aspects of Code Velocity
Gunnar Kudrjavets, Nachiappan Nagappan, Ayushi Rastogi
This paper investigates how the duration of various code review periods changes over a projects' lifetime. We study four open-source software (OSS) projects: Blender, FreeBSD, LLVM…
Who Ate My Memory? Towards Attribution in Memory Management
Gunnar Kudrjavets, Ayushi Rastogi, Jeff Thomas +1
To understand applications' memory usage details, engineers use instrumented builds and profiling tools. Both approaches are impractical for use in production environments or deplo…
When malloc() Never Returns NULL -- Reliability as an Illusion
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
For decades, the guidance given to software engineers has been to check the memory allocation results. This validation step is necessary to avoid crashes. However, in user mode, in…