Repository navigation
Make variables and callstack to reload asynchronously [feature request] #22807
Description
- VSCode Version: 1.10.2
- OS Version: Ubuntu 14.04
When debugging with gdb doing step over takes a lot of time. Debugger is blocked until variables and call stack is reloaded.
Activity
isidorn commentedon Mar 20, 2017
Well we fetch variables and the call stack asynchroniously so the whole UI should not be blocked.
However of course that you can not step over until we have the call stack and that you can not inspect variables until those are fetched.
If you only see this slowness for the gdb debugger then I suggest you open this issue on the gdb side and suggest that they mark more Scopes as
expensive.Another thing the gdb debugger can improve is to use
indexedVariablesfor cases where there are scopes and variables with a large number of children.I believe VSCode is already doing everything here it can thus closing as designed
By the way here is the gdb debugger repository
https://github.com/WebFreak001/code-debug
fyi Jan Jurzitza (@WebFreak001)
wcscmp commentedon Apr 28, 2017
Maybe it is debugger specific thing but some debuggers can do a step over before variables are fetched and call stack is known. Can you please allow it to be configurable by debugger plugin?
isidorn commentedon Apr 28, 2017
Well call stack has to be known in order for the step to be "done", since the call stack deteremines the step location.
While the variables are fetched asynchrounisly. Namely, you should be able to step while the slow variables request is being completed (shown in the variables tree as a loading spinning icon)