235 citations
- Carnegie Mellon UniversityUS5 papers
- University of GroningenNL5 papers
- University of WashingtonUS5 papers
- Meta (United States)US4 papers
- University of Southern CaliforniaUS4 papers
- Princeton UniversityUS3 papers
- BC Platforms (Finland)FI2 papers
- Google (United States)US2 papers
- Max Planck Institute for InformaticsDE2 papers
- Northwestern UniversityUS2 papers
- Pennsylvania State UniversityUS2 papers
- Southern States UniversityUS2 papers
5 papers · 2 filters
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…
There Ain't No Such Thing as a Free Custom Memory Allocator
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
Using custom memory allocators is an efficient performance optimization technique. However, dependency on a custom allocator can introduce several maintenance-related issues. We pr…
Mining Code Review Data to Understand Waiting Times Between Acceptance and Merging: An Empirical Analysis
Gunnar Kudrjavets, Aditya Kumar, Nachiappan Nagappan +1
Increasing code velocity (or the speed with which code changes are reviewed and merged) is integral to speeding up development and contributes to the work satisfaction of engineers…
Quantifying Daily Evolution of Mobile Software Based on Memory Allocator Churn
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
The pace and volume of code churn necessary to evolve modern software systems present challenges for analyzing the performance impact of any set of code changes. Traditional method…
The Unexplored Terrain of Compiler Warnings
Gunnar Kudrjavets, Aditya Kumar, Nachiappan Nagappan +1
The authors' industry experiences suggest that compiler warnings, a lightweight version of program analysis, are valuable early bug detection tools. Significant costs are associate…