1 # Debugging VSCode plugin and the language server
5 - Install [LLDB](https://lldb.llvm.org/) and the [LLDB Extension](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb).
6 - Open the root folder in VSCode. Here you can access the preconfigured debug setups.
8 <img height=150px src="https://user-images.githubusercontent.com/36276403/74611090-92ec5380-5101-11ea-8a41-598f51f3f3e3.png" alt="Debug options view">
10 - Install all TypeScript dependencies
18 * All debug configurations open a new `[Extension Development Host]` VSCode instance
19 where **only** the `rust-analyzer` extension being debugged is enabled.
20 * To activate the extension you need to open any Rust project folder in `[Extension Development Host]`.
23 ## Debug TypeScript VSCode extension
25 - `Run Installed Extension` - runs the extension with the globally installed `rust-analyzer` binary.
26 - `Run Extension (Debug Build)` - runs extension with the locally built LSP server (`target/debug/rust-analyzer`).
28 TypeScript debugging is configured to watch your source edits and recompile.
29 To apply changes to an already running debug process, press <kbd>Ctrl+Shift+P</kbd> and run the following command in your `[Extension Development Host]`
32 > Developer: Reload Window
35 ## Debug Rust LSP server
37 - When attaching a debugger to an already running `rust-analyzer` server on Linux you might need to enable `ptrace` for unrelated processes by running:
40 echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
44 - By default, the LSP server is built without debug information. To enable it, you'll need to change `Cargo.toml`:
50 - Select `Run Extension (Debug Build)` to run your locally built `target/debug/rust-analyzer`.
52 - In the original VSCode window once again select the `Attach To Server` debug configuration.
54 - A list of running processes should appear. Select the `rust-analyzer` from this repo.
56 - Navigate to `crates/rust-analyzer/src/main_loop.rs` and add a breakpoint to the `on_request` function.
58 - Go back to the `[Extension Development Host]` instance and hover over a Rust variable and your breakpoint should hit.
60 If you need to debug the server from the very beginning, including its initialization code, you can use the `--wait-dbg` command line argument or `RA_WAIT_DBG` environment variable. The server will spin at the beginning of the `try_main` function (see `crates\rust-analyzer\src\bin\main.rs`)
63 while d == 4 { // set a breakpoint here and change the value
68 However for this to work, you will need to enable debug_assertions in your build
70 RUSTFLAGS='--cfg debug_assertions' cargo build --release
75 - [Debugging TypeScript VScode extension](https://www.youtube.com/watch?v=T-hvpK6s4wM).
76 - [Debugging Rust LSP server](https://www.youtube.com/watch?v=EaNb5rg4E0M).
80 ### Can't find the `rust-analyzer` process
82 It could be a case of just jumping the gun.
84 The `rust-analyzer` is only started once the `onLanguage:rust` activation.
86 Make sure you open a rust file in the `[Extension Development Host]` and try again.
88 ### Can't connect to `rust-analyzer`
90 Make sure you have run `echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope`.
92 By default this should reset back to 1 every time you log in.
94 ### Breakpoints are never being hit
96 Check your version of `lldb`. If it's version 6 and lower, use the `classic` adapter type.
97 It's `lldb.adapterType` in settings file.
99 If you're running `lldb` version 7, change the lldb adapter type to `bundled` or `native`.