Report stack in DAP
Clarification and motivation
Once we can launch contract and stop its execution, we should be able to display the current stack through DAP in a nice way.
The stopped
event has threadId parameter. For that thread id the editor can request a stack trace, the debugger should respond with a list of stack frames. Then for each frame editor can request its scopes with ScopesRequest
and finally for each scope -- its variables, using variablesReference
parameter and VariablesRequest
.
We should return a list of indexed variables as a response to that request. Each variable is one cell of our stack.
Acceptance criteria
Debugger displays stack after each step.
Edited by Maxim Koltsov