ABSTRACT
Code instrumentation is a mechanism that allows modules of programs to be completely rewritten at runtime. With the advent of virtual machines, this type of functionality is becoming more and more interesting because it allows the introduction of new functionality after an application has been deployed, easy implementation of aspect-oriented programming, performing security verifications, dynamic software upgrading, among others.
The Runtime Assembly Instrumentation Library (RAIL) is one of the first frameworks to implement code instrumentation in the.NET platform. It specifically addresses the limitations that exist between the reflection capabilities of.NET and its code emission functionalities. RAIL gives the programmer an object-oriented vision of the code of an application, allowing assemblies, modules, classes, references and even intermediate code to be easily manipulated.
This paper addresses the design of an implementation of RAIL along with the difficulties and lessons learnt in building a framework for code instrumentation in.NET.
- Syme, D. ILX: Extending the.NET Common IL for Functional Language Interoperability, MS Research, Cambridge, September 2001. Available at: http://research.microsoft.com/projects/ilx.Google Scholar
- Lam, J. Cross-Language Load-Time Aspect Weaving on Microsoft's Common Language Runtime. Demonstration at the AOSD2002, Netherlands, 2002.Google Scholar
- Lafferty, D., and Cahill, V. Language-Independent Aspect-Oriented Programming. In Proc. OOPSLA 2003 <http://oopsla.acm.org/oopsla2003/>, Anaheim, USA, October 2003. Google ScholarDigital Library
- Dahm, M. Byte Code Engineering. In JIT '99, Düsseldorf, Germany, September 1999.Google Scholar
- Cohen, G., Chase, J., and Kaminsky, D. Automatic Program Transformation with JOIE. In USENIX 1998 Annual Technical Conference, New Orleans, USA, 1998. Google ScholarDigital Library
- Chiba, S., and Nishizawa M. An Easy-to-Use Toolkit for Efficient Java Bytecode Translators <http://www.csg.is.titech.ac.jp/paper/chiba-gpce03.pdf>. In Proc. GPCE '03, LNCS 2830, Springer-Verlag, 2003. Google ScholarDigital Library
- Ferber, J. Computational Reflection in Class Based Object-Oriented Languages. In Proc. OOPSLA '89, New Orleans, USA, October 1989. Google ScholarDigital Library
- J. Malenfant, C. Dony, and P. Cointe. Behavioral Reflection in a Prototype-Based Language. In Proc. IMSA '92, Tokyo, 1992.Google Scholar
- BCEL Project, Apache Software Foundation, 2003. Available at: http://jakarta.apache.org/bcel/projects.html.Google Scholar
- Keller, R., and Hölzle, U., Binary Component Adaptation. In Proc. ECOOP '98, Brussels, Belgium, July 1998. Google ScholarDigital Library
Index Terms
- RAIL: code instrumentation for .NET
Recommendations
RAIL: code instrumentation for .NET
SAC '05: Proceedings of the 2005 ACM symposium on Applied computingCode instrumentation is a mechanism that allows modules of programs to be completely rewritten at runtime. With the advent of virtual machines, this type of functionality is becoming more interesting because it allows the introduction of new ...
Fast snapshot migration using static code instrumentation: work-in-progress
EMSOFT '18: Proceedings of the International Conference on Embedded SoftwareDue to the portability advantage of web apps, we can easily save the app execution state at a device and restore it at another device, allowing app migration. Since the execution of the application includes JavaScript internal states such as closures or ...
SymFusion: Hybrid Instrumentation for Concolic Execution
ASE '22: Proceedings of the 37th IEEE/ACM International Conference on Automated Software EngineeringConcolic execution is a dynamic twist of symbolic execution designed with scalability in mind. Recent concolic executors heavily rely on program instrumentation to achieve such scalability. The instrumentation code can be added at compilation time (...
Comments