Open artem-ogre opened 2 years ago
@vadimcn do you have any details on this? Is there a LLDB bug tracking this issue? I'm currently hitting this as well.
Just stating what's already known I guess, but, yes, it's an LLDB issue as I had the same problem in CLion.
LLDB issue is tracked here: https://github.com/llvm/llvm-project/issues/54250
As it turns out this issue was introduced in llvm-14 and fixed in llvm-15. To fix this issue in vscode-lldb either roll back to llvm-13 or update to llvm-15 which will come out in a few days.
This extension uses a bundled llvm-15 now. The issue still persists for me on windows.
(base) PS C:\Users\[myusername]\.vscode\extensions\vadimcn.vscode-lldb-1.8.1\lldb\bin> .\lldb.exe --version
lldb version 15.0.0-custom
I fetched an llvm-13 by installing this extension in version 1.6.10. Either version 1.6.10 nor the current version 1.8.1 with llvm-13 works as a workaround.
I made a very small example project and stepping into a function using F11 (Step into) here works. When I now want to step over that function using F10 (Step over) vscode steps into the function, too. So it is just the opposite of what happened in the other project.
Please note that the PDB debug info format on Windows is pretty different from "normal" code path in LLDB with its own set of bugs.
Could it be possible to tweak lldb.library
handling to support ${workspaceFolder}
as part of lldb.so
path? Something like
"lldb.library": "${workspaceFolder}/llvm/lib/liblldb.so"
?
I did quick googling and seems like ${workspaceFolder}
couldn't be used within settings.json
scope, but I'm not fully sure - electron/vscode and related technologies are absolutely out of my scope.
Adding such feature solves two issues:
OS: Ubuntu 20.04 VSCode version: VSCodium
CodeLLDB version: 1.6.10 Compiler: gcc Debuggee: c++ binary
When I attempt to step-into a function the debugger will not enter it but jump to the next line at the call-site instead.
When setting a break-point inside the function it is hit without problems. Also it is possible to step-into the function after multiple
thread step-inst
commands in the debugger console.My launch.json has nothing special:
Verbose log after issuing `thread step-in`
x86_64-linux-gcc