Closed lylythechosenone closed 1 year ago
I'm having the same issue. Using Windows WSL 2.
Program runs but breakpoints never get hit. Even when adding breakpoints in the console.
{
"version": "0.2.0",
"configurations": [
{
"name": "Debug (LLDB)",
"type": "lldb",
"request": "launch",
"program": "${workspaceFolder}/Application",
"args": [
],
"cwd": "${workspaceFolder}",
"env": {
"LD_LIBRARY_PATH": "/home/lib_a64/code/bin"
},
"preLaunchTask": "build"
}
]
}
@lylythechosenone: This sounds like a source path mapping issue.
You can also try a new feature in v1.9.1, which allows resolving breakpoints using file name only, like it works in the console. See breakpointMode
.
@GimpMaster: Given that you are using Windows/WSL and the original issue is about Linux, it is unlikely that they are related.
... Even when adding breakpoints in the console.
I strongly suspect this isn't a CodeLLDB issue, but rather something about the debug info for your binary. Try to diagnose it as described here.
But Microsoft C/C++ plugin works fine.
OS: MacOS Ventura 13.1 (aarch64-apple-darwin) VSCode version: 1.77.1 CodeLLDB version: 1.9.0 Compiler: rust nightly 1.70.0 Debuggee: linux-like kernel within qemu (raw binary in qemu with ELF symbol file in lldb)
Setting breakpoints in vscode does not work (sometimes). Setting them in the console always works, but breakpoints set in vscode are never reached. If I set a breakpoint on a function in the console, further breakpoints in the same function (possibly same file) work fine.
This is my launch config:
Log shows nothing unusual, just setting the breakpoints by filenames and lines.