The potential of omniscient debugging for aspect-oriented programming languages

Marnix van 't Riet, Haihan Yin, Christoph Bockisch

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    2 Citations (Scopus)
    101 Downloads (Pure)

    Abstract

    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.
    Original languageUndefined
    Title of host publicationProceedings of the International Workshop on Comprehension of Complex Systems (CoCoS 2013)
    Place of PublicationNew York
    PublisherAssociation for Computing Machinery
    Pages13-16
    Number of pages4
    ISBN (Print)978-1-4503-1863-1
    DOIs
    Publication statusPublished - Mar 2013
    EventInternational Workshop on Comprehension of Complex Systems (CoCoS 2013), Fukuoka, Japan: Proceedings of the International Workshop on Comprehension of Complex Systems (CoCoS 2013) - New York
    Duration: 1 Mar 2013 → …

    Publication series

    Name
    PublisherACM

    Conference

    ConferenceInternational Workshop on Comprehension of Complex Systems (CoCoS 2013), Fukuoka, Japan
    CityNew York
    Period1/03/13 → …

    Keywords

    • EWI-23287
    • CR-D.2.5
    • CR-D.3.2
    • IR-85834
    • Advanced dispatching
    • Aspect Oriented Programming
    • METIS-296408
    • omniscient debugging

    Cite this