forked from OSchip/llvm-project
b9139acb85
VScode now sends a "scopes" DAP request immediately after any expression evaluation. This scopes request would clear and invalidate any non-scoped expandable variables in g_vsc.variables, causing later "variables" request to return empty result. The symptom is that any expandable variables in VScode watch window/debug console UI to return empty content. This diff fixes this issue by only clearing the expandable variables at process continue time. To achieve this, we have to repopulate all scoped variables during context switch for each "scopes" request without clearing global expandable variables. So the PR puts the scoped variables into its own locals/globals/registers; and all expandable variables into separate "expandableVariables" list. Also, instead of using the variable index for "variableReference", it generates a new variableReference id each time as the key of "expandableVariables". As a further new feature, this PR adds a new "expandablePermanentVariables" which has the lifetime of debug session. Any expandable variables from debug console are added into this list. This enables users to snapshot expanable old variable in debug console and compare with new variables if desire. Reviewed By: clayborg Differential Revision: https://reviews.llvm.org/D105166 |
||
|---|---|---|
| .. | ||
| attach | ||
| breakpoint | ||
| breakpoint-events | ||
| completions | ||
| console | ||
| coreFile | ||
| disconnect | ||
| evaluate | ||
| launch | ||
| module | ||
| runInTerminal | ||
| stackTrace | ||
| step | ||
| variables | ||
| categories | ||