ACM Home Page
Please provide us with feedback. Feedback
A generic and reflective debugging architecture to support runtime visibility and traceability of aspects
Full text PdfPdf (730 KB)
Source
Aspect-oriented software development archive
Proceedings of the 8th ACM international conference on Aspect-oriented software development table of contents
Charlottesville, Virginia, USA
SESSION: Testing and verification table of contents
Pages 173-184  
Year of Publication: 2009
ISBN:978-1-60558-442-3
Authors
Wouter De Borger  KULeuven, Leuven, Belgium
Bert Lagaisse  KULeuven, Leuven, Belgium
Wouter Joosen  KULeuven, Leuven, Belgium
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 90,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1509239.1509263
What is a DOI?

ABSTRACT

In this paper we present a generic, mirror-based debugging architecture that supports runtime visibility and traceability of aspect oriented (AO) software systems. Runtime visibility supports inspection of an executing AO-system in terms of AO programming abstractions and code artifacts such as (dynamic) aspects, advices, pointcuts, aspect instances and advice applications. Runtime traceability supports inspection of the stack to identify advices that could have been executed, that are being executed, or that may be executed later. Additionally, traceability supports identification and inspection of the pointcut that causes a specific advice.

We have created a mirror based architecture that offers introspection support including an aspect-aware breakpoint model for AOP-related runtime events. We introduce the concept of hook frames to trace joinpoints and their advices on the stack.

We validate the genericity of our architecture in two instantiations -- JBoss AOP and AspectJ/ABC -- and evaluate both instantiations by applying concrete debugging scenarios.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
M. Eaddy, A. V. Aho, W. Hu, P. McDonald, and J. Burger. Debugging aspect-enabled programs. In Software Composition, pages 200--215, 2007.
 
4
Eclipse Foundation. Aspectj development tools. http://www.eclipse.org/ajdt/. access: 23/05/08.
 
5
P. Grace, B. Lagaisse, E. Truyen, and W. Joosen. A reflective framework for fine-grained adaptation of aspect-oriented compositions. In Software Composition, pages 215--230, 2008.
 
6
7
 
8
K. Mehner and A. Rashid. Towards a standard interface for runtime inspection in aop environments. OOPSLA Workshop on Tools for AOSD, 2002.
 
9
10
11
 
12
13
 
14
Sun Microsystems. Java Platform Debugger Architecture, java se 6.0 edition. access: 23/05/08.
 
15
E. Tanter. From Metaobject Protocols to Versatile Kernels for AOP. PhD thesis, University of Nantes, France, 2004.
16

Collaborative Colleagues:
Wouter De Borger: colleagues
Bert Lagaisse: colleagues
Wouter Joosen: colleagues