DSL Debugger exits the dsl code and enters java code [message #1830793] |
Tue, 04 August 2020 06:24 |
Loredana Hozan Messages: 34 Registered: January 2019 |
Member |
|
|
Hello, we have created a debugger for our dsl, the generated code gets processed by another framework, when we debug the dsl code we have the following:
-We have a DSL that calls generated code using lamba expressions that are then passed to an underlying framework.
-When we are debugging the DSL code, and we do a step over, sometimes it happens that the next line of DSL is mapped to java code in the lambda expression. When we do this, the debugger works correctly, even though, there was a big jump in the call stack from the previous DSL line. The new line is being called in the framework, so we have a lot of intermediate functions that don't belong to the DSL generated code.
-When the code in the lambda expression is finished, the step over tries to go the calling code, which is not DSL generated code but framework code, thus we lose the mapping and we get weird errors because we don't even have the source code of the framework.
This behavior seems inconsistent with the behavior of the step over when we enter the framework, since entering the framework was transparent but the exit from the framework was not.
Is this a normal Xtext/Debugger behavior? Which is the official way of having debug working as we expect, i.e. just jumping from DSL code, to DSL code and not jumping to java generated code occasionally.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02398 seconds