Closed gezihuzi closed 1 year ago
Strange indeed.... How did you install the extension? Is this a plain Windows.environment or some emulation like WSL?
Strange indeed.... How did you install the extension? Is this a plain Windows.environment or some emulation like WSL?
Plain Windows, not WSL.
I search for codelldb
in VSCode on macOS and install it, then sync the account configuration to Windows.
I think I may have found the problem. The configuration of my account synchronized the plugin's configuration information, and lldb:library was manually (or automatically) set to the above path.
After removing the above lldb:library
configuration, debugging works fine on both macOS and Windows.
I think I may have found the problem. The configuration of my account synchronized the plugin's configuration information, and lldb:library was manually (or automatically) set to the above path.
After removing the above lldb:library
configuration, debugging works fine on both macOS and Windows.
OS: Windows 11 v22H2-22621.1778 VSCode version: v1.79.2 stable CodeLLDB version: 1.9.2 Compiler: rustc Debugger: lldb.exe(C:\Users*\scoop\apps\llvm\current\bin\lldb.EXE)
The plugin cannot find the correct path to the lldb executable under Windows.
I tried to use lldb to run tauri application on my Windows computer, but I couldn't start lldb properly for debugging, I checked the relevant output of lldb and found the path (Error: ENOENT: no such file or directory, stat 'C:\Applications\Xcode. app\Contents\SharedFrameworks\LLDB.framework\Versions\A\LLDB') is very strange, theoretically this path should be the path of the application under macOS, somehow it will find the executable file of lldb by this path under Windows.
Verbose log