-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Step-into behaves as step-over (jumps over function) #587
Comments
@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: llvm/llvm-project#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.
|
I fetched an llvm-13 by installing this extension in version 1.6.10. |
I made a very small example project and stepping into a function using F11 (Step into) here works. |
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
I did quick googling and seems like 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
The text was updated successfully, but these errors were encountered: