Aspect-oriented programming improve program modularity and meanwhile decreases program comprehensibility, because it can alter the program behavior implicitly. Sometimes, the implicit behavior even varies in different runtime context. To fix bugs related to aspect-oriented entities, programmers need to fully comprehend their actual behavior before taking treatments. However, in some commonly encountered debugging scenarios, existing tools fall short in providing desired information. In this paper, we have described two AO-specific debugging scenarios that require to use the program execution history. We discuss our design ideas, which are (1) a model defining AO-specific events and (2) a visualization consisting of three states, which shows different levels of details.
|Conference||International Workshop on Comprehension of Complex Systems (CoCoS 2013), Fukuoka, Japan|
|Period||1/03/13 → …|
- Advanced dispatching
- Aspect Oriented Programming
- omniscient debugging