A generic instrumentation framework for collecting dynamic information

ABSTRACT

Performing empirical research in software testing involves executing a set of subjects against one or more test suites and measuring some characteristics of these executions. Such measures are often collected using ad-hoc instrumentation, by inserting probes in the code that collect and report dynamic information at run-time. Another possible approach is to collect the needed information by leveraging capabilities of the runtime system. Both these approaches usually result in measurement tools that are not flexible and are, thus, hard to reuse and modify. To address this problem, we present a generic framework for collecting information on the runtime behavior of a Java program. The framework allows for easily collecting different kinds of dynamic information for a set of executions of the program, such as coverage and profiling of various code entities and program traces at different levels. The framework also lets users easily define how to process the collected information. In the paper, we also present a case study that we performed to evaluate the framework, and that shows its effectiveness and efficiency.

REFERENCES

• 1: Aspectj project. http://eclipse.org/aspectj/.
• 2: Byte-Code Engineering Library (BCEL). http://jakarta.apache.org/bcel/.
• 3: Java Architecture for Bytecode Analysis (JABA). http://www.cc.gatech.edu/aristotle/Tools/jaba.html.
• 4: Java Instrumentation API (JIAPI). http://jiapi.sourceforge.net/.
• 5: Java Instrumentation Engine (JIE). http://www.forum2.org/eran/jie/.
• 6: Java Runtime Analysis Toolkit (JRAT). http://jrat.sourceforge.net/index.html.
• 7: Java Virtual Machine Debugging Interface (JVMDI). http://java.sun.com/j2se/1.3/docs/guide/jpda/jvmdi-spec.html.
• 8: Java Virtual Machine Profiler Interface (JVMPI). http://java.sun.com/j2se/1.4.2/docs/guide/jvmpi/jvmpi.html.