2015
DOI: 10.1007/978-3-319-19584-1_3
|View full text |Cite
|
Sign up to set email alerts
|

Extensible Debugger Framework for Extensible Languages

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 12 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…Still for grammar-based compiled DSLs, Lindeman et al [32] proposes a similar approach were the source DSL program is instrumented with debug information. In the context of extensible languages, Pavletic et al [33] proposes a framework to define and extend debuggers. Das et al [34] describe a framework to monitor at the domain-level the execution of models that were compiled to code, with a strong focus on UML-RT.…”
Section: Threats To Validitymentioning
confidence: 99%
“…Still for grammar-based compiled DSLs, Lindeman et al [32] proposes a similar approach were the source DSL program is instrumented with debug information. In the context of extensible languages, Pavletic et al [33] proposes a framework to define and extend debuggers. Das et al [34] describe a framework to monitor at the domain-level the execution of models that were compiled to code, with a strong focus on UML-RT.…”
Section: Threats To Validitymentioning
confidence: 99%
“…The advantages of debugging at the model-level have been discussed in the literature, e.g. in [37]. Existing approaches mainly focus on debugger frameworks for dedicated domain-specific languages and are not applicable to mainstream Java programs.…”
Section: Visual Debuggingmentioning
confidence: 99%
“…However, MPS does not specifically support the development of debuggers for languages that support modular language extensions. To address this shortcoming, we have developed our own debugger framework for extensible languages as part of mbeddr [65]. It works by running a debugger (typically gdb in case of mbeddr C) on the generated code.…”
Section: Rq3: Mechanisms For Managing Complexitymentioning
confidence: 99%