diff options
| author | Greg Clayton <gclayton@fb.com> | 2022-09-20 20:58:08 -0700 |
|---|---|---|
| committer | Greg Clayton <gclayton@fb.com> | 2022-09-29 10:55:16 -0700 |
| commit | 4017d86df98faa53bbb1a0acc4e8e58d2b6f2608 (patch) | |
| tree | 92aaafee9681b09dc9cfc3c9ecc6ca688acc69ad /clang/lib/Frontend/InitPreprocessor.cpp | |
| parent | b3a0bed5fb8766dcf27583ab1f73edc6e7232657 (diff) | |
| download | llvm-4017d86df98faa53bbb1a0acc4e8e58d2b6f2608.zip llvm-4017d86df98faa53bbb1a0acc4e8e58d2b6f2608.tar.gz llvm-4017d86df98faa53bbb1a0acc4e8e58d2b6f2608.tar.bz2 | |
When there are variable errors, display an error in VS Code's local variables view.
After recent diffs that enable variable errors that stop variables from being correctly displayed when debugging, allow users to see these errors in the LOCALS variables in the VS Code UI. We do this by detecting when no variables are available and when there is an error to be displayed, and we add a single variable named "<error>" whose value is a string error that the user can read. This allows the user to be aware of the reason variables are not available and fix the issue. Previously if someone enabled "-gline-tables-only" or was debugging with DWARF in .o files or with .dwo files and those separate object files were missing or they were out of date, the user would see nothing in the variables view. Communicating these errors to the user is essential to a good debugging experience.
Differential Revision: https://reviews.llvm.org/D134333
Diffstat (limited to 'clang/lib/Frontend/InitPreprocessor.cpp')
0 files changed, 0 insertions, 0 deletions