| Issue |
171913
|
| Summary |
LLDB DAP assertion failure
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
sedymrak
|
I am using VSCode IDE.
Until recently, I was using `codelldb` VSCode extension for debugging C++ code.
Now I am experimenting with "LLDB DAP" VSCode extension.
I have compiled `lldb` with debugging symbols so that I can debug it in VSCode (using the "LLDB DAP" VSCode extension).
I have noticed that whenever the control flow enters the `ValueObject::GetExpressionPath` method (defined in the `lldb/source/ValueObject/ValueObject.cpp` file), as soon as I start typing something in the "DEBUG CONSOLE" (it does not matter what), the following error appears in the "DEBUG CONSOLE":
```
lldb-dap: /home/me/git/other/llvm-project/main/0/clang/lib/Sema/SemaAccess.cpp:750: AccessResult HasAccess(Sema &, const EffectiveContext &, const CXXRecordDecl *, AccessSpecifier, const AccessTarget &): Assertion `Access == AS_private || Access == AS_protected' failed.
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Stack dump:
0. Program arguments: /home/me/git/other/llvm-project/main/0/build--main--Debug--mold--make/bin/lldb-dap
```
and the following message appears in the "LLDB-DAP" console (accessible via the combo-box in the "OUTPUT" pane:
```
2025-12-11 22:30:49.196 [error] Error: read error
at Socket.<anonymous> (file:///usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:132:1948)
at Socket.emit (node:events:531:35)
at Pipe.<anonymous> (node:net:346:12)
```
Afterwords, the "DEBUG CONSOLE" is unresponsive.
I have configured VSCode to use `lldb-dap` built from the `main` branch by adding the following entry:
```
"lldb-dap.executable-path": "/home/me/git/other/llvm-project/main/1/build--main--Release--ld--make/bin/lldb-dap",
```
to the corresponding `.vscode/settings.json` file.
However, the same error can be observed even if I use `lldb-dap` from `release-19.x` branch.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
