Debugging Object Teams programs
Debugging support has been extended in order to help debugging OT/J programs.
Debugging OT/J may give rise to a new kind of questions: is a declared
callin binding actually firing at run-time? In order to analyze this question
a developer may need to investigate:
Investigating question 1 is supported by the new team monitor view,
support for question 2 is provided by enhancements of the debug view and its stepping actions.
A special view exists for monitoring which team instances have been created and whether each
of them is currently active or not. When debugging callin bindings which do not trigger while
they are intended to do so, the team monitor should provide first help to find out whether
there is any active instance of the team being considered. If no active instance exists,
callins can not trigger. Read more...
The byte code into which OT/J programs are translated has some significant differences
to the original source code. In order to hide some generated code and to provided
convenient stepping even through declarative method bindings, the debug view has
been enhanced for OT/J. Read more...
By default the variables view hides some internal fields that are generated by the compiler.
However, in some situations these variables might come handy for inspecting the linkage between
role/base/team instances. For that reason, filtering of these variables
can be toggled from the variable view's menu: Java > Show OT/J Internal Variables.
The same holds for the detail drill down of the team monitor.
- Has a team instance be created and activated?
- Is the callin blocked by either a guard predicate or a