Tracking load-time configuration options
Open Access
- 15 September 2014
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 445-456
Abstract
Highly-configurable software systems are pervasive, although configuration options and their interactions raise complexity of the program and increase maintenance effort. Especially load-time configuration options, such as parameters from command-line options or configuration files, are used with standard programming constructs such as variables and if statements intermixed with the program's implementation; manually tracking configuration options from the time they are loaded to the point where they may influence control-flow decisions is tedious and error prone. We design and implement Lotrack, an extended static taint analysis to automatically track configuration options. Lotrack derives a configuration map that explains for each code fragment under which configurations it may be executed. An evaluation on Android applications shows that Lotrack yields high accuracy with reasonable performance. We use Lotrack to empirically characterize how much of the implementation of Android apps depends on the platform's configuration options or interactions of these options.Keywords
Funding Information
- Bundesministerium für Forschung, Technologie und Raumfahrt (01IS12043B, EC SPRIDE)
- National Science Foundation (1318808)
- Deutsche Forschungsgemeinschaft (RUNSECURE)
- Hessian LOEWE excellence initiative (CASED)
This publication has 24 references indexed in Scilit:
- Feature maintenance with emergent interfaces2014
- Exploring variability-aware execution for testing plugin-based web applications2014
- Which configuration option should I change?2014
- Regression tests to expose change interaction errors2013
- SPL LIFT2013
- Do background colors improve program comprehension in the #ifdef hell?Empirical Software Engineering, 2012
- Integration Testing of Software Product Lines Using Compositional Symbolic Execution2012
- Precomputing possible configuration error diagnoses2011
- Thin slicing2007
- Using version control data to evaluate the impact of software tools: a case study of the Version EditorIEEE Transactions on Software Engineering, 2002