Execution Trace Analysis Through Massive Sequence and Circular Bundle Views

Bas Cornelissen, Danny Holten, Andy Zaidman, Leon Moonen, Jarke J. van Wijk, and Arie van Deursen

This page provides an on line appendix to the following papers:

• B. Cornelissen, D. Holten, A. Zaidman, L. Moonen, J.J. van Wijk, and A. van Deursen (2007). Understanding Execution Traces Using Massive Sequence and Circular Bundle Views. In Proceedings of the 15th International Conference on Program Comprehension (ICPC), pp. 49-58, IEEE Computer Society. (Also appeared as technical report TUD-SERG-2007-009)

• B. Cornelissen, A. Zaidman, D. Holten, L. Moonen, A. van Deursen, and J.J. van Wijk (2008). Execution Trace Analysis Through Massive Sequence and Circular Bundle Views. In Journal of Systems & Software (JSS), 81(11), pp. 2252-2268, Elsevier. (Also appeared as technical report TUD-SERG-2008-008)

Online Appendix

Tool download

The tool is documented and downloadable on the EXTRAVIS homepage.

Example inputs are included in the distribution.

Figures

High resolution, full color versions of the figures in the papers are displayed below. The images can be opened in their original size by clicking on them.

JSS figures

• Figure 1: Call relations within a program shown using linear edges (left) and using hierarchical edge bundles (right).

• Figure 2: Full view of an entire Cromod trace.

• Figure 3: Using Importance-Based Anti-Aliasing (IBAA) to visualize outlier calls.

• Figure 4: Collapsing the ``model'' and ``util.fileio'' packages in the Cromod trace.

• Figure 5: Circular view of Cromod's initialization phase.

• Figure 6: Zoomed massive sequence view of Cromod's second phase, focusing on a periodic fragment.

• Figure 7: Execution scenario for JHotDraw, in which five different figures are inserted in three distinct drawings.

• Figure 8: (a) Full trace of the JHotDraw scenario. (b) Zooming in on the ``new drawing'' feature and the subsequent figure insertions.

• Figure 9: Circular bundle views of two alleged figure drawings, indicating very slight differences.

• Figure 10: Massive sequence view of the entire Checkstyle trace (left), and zoomed views of each of its five phases (right).

• Figure 11: Full view of a recurrent sequence in Checkstyle's first phase, in which the circular view indicates the receiving classes and the order in which they are processed.

• Figure 12: Focusing on the transition between Checkstyle's first and second phase. The tooltips provide information on the call sites.

• Figure 13: Looking up associated source code fragments.

ICPC'07 figures

• Figure 5: (a) Full trace of the JPacman scenario. (b) Zooming in on the ``player dies'' feature. (c) Highlighting an interaction.

• Figure 6: Circular, temporal view of the ``player dies'' feature that shows run time information.