-
### This is a weird problem, when I tried to debug with vscode's plugin "CodeLLDB"
When step into the `for` loop, my variables and watches are all missing like this:
![Missing variables and watche…
-
As prompted by https://discourse.llvm.org/t/flang-fortran-plugin-for-lldb-status/81301, this is a tracking issue for Fortran support. It existing doesn't mean work is being done or not, it's just a pl…
-
After setting `target.debug-file-search-paths` on command line, `lldb.debugger.GetSetting("target.debug-file-search-paths")` is unable to show the value, while it works for `target.source-map`.
```…
-
**Is your feature request related to a problem? Please describe.**
The Swift extension currently resolves the Swift toolchain LLDB dylib used by CodeLLDB by following the symbolic link, if any, from …
-
On macOS, if the latest llvm 18.1.8 is installed from brew, the vscode's debugger can't stop at the line selected.
-
When debugging clang static analyzer, the output of evaluating dump of ProgramState of ExplodedNode seems does not work in LLDB, the issue is weirded that I cannot describe it in simple one or two sta…
-
-
Hi,
is it possible to add a debug feature called "Jump To Cursor" to the context menu in a vscode editor while debugging?
"Goto Cursor" already exists, so the new feature is an addition.
Best r…
-
When I compile the code below with `clang main.cc -o main --std=c++23 -stdlib=libc++ -lc++ -g -O0`.
```c++
#include
int main(int argc, char **argv) {
_BitInt(64) i64 = 42; // Works
_BitI…
-
1. In LLVM 18.1.8, LLDB aborted while executing `print` or `fr v` command on line 16 of the binary generated with `-g -O3`,
```
clang -g -O3 320.c -o 320.out
lldb 320.out
(lldb) b 320.c:16
Breakp…