Replies: 2 comments 1 reply
-
lldb does not work with classic WSL - just try manually debbung using lldb, it just gets stuck/doesn't to anything either. See microsoft/WSL#2796 and so on. |
Beta Was this translation helpful? Give feedback.
-
Hi. I am also using Visual Studio Code remote connection to write code and debug it on a remote computer (either a real Linux host via the Remote SSH connection or the WSL via the WSL extension). This is what ls prints in ~/.vscode-server/extensions/vadimcn.vscode-lldb-1.10.0 on the remote Linux host:
And this is what it prints on the WSL:
Either Visual Studio Code or the extension installation routine failed to detect correctly the operating system. Regards, |
Beta Was this translation helpful? Give feedback.
-
I have a C/C++ test example under WSL-Ubuntu 20.04 LTS, Win10:
The code of project main.cpp
Unfortunately, I can't debug it - this is my launch.json
I have installed under WSL:Ubuntu clang, lldb, CodeLLD (other plugins) under WSL:Ubuntu 20.04
How to properly configure vscode launch.json to have C/C++ code compiling and debugging with clang/lldb?
Thank you!
Note: Per StackOverflow comment: if cpptools is installed, it will conflict with clang+CodeLLDB
Beta Was this translation helpful? Give feedback.
All reactions