<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>src/tools/rust-analyzer/docs/dev/debugging.md - fork/rust @ master</title>
<meta name="description" content="src/tools/rust-analyzer/docs/dev/debugging.md in fork/rust at master.">
<meta property="og:title" content="src/tools/rust-analyzer/docs/dev/debugging.md - fork/rust @ master">
<meta property="og:description" content="src/tools/rust-analyzer/docs/dev/debugging.md in fork/rust at master.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="master" data-tip="3bcad65fbf67b6edf87c949531fbc13435882e6b">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/rust</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/rust</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">bors</span><span class="commit-message" data-commit="3bcad65fbf67b6edf87c949531fbc13435882e6b">Auto merge of #103046 - JanBeh:PR_clarify_cmp_terminology, r=workingjubilee</span><span class="snapshot-sha sha" data-commit="3bcad65fbf67b6edf87c949531fbc13435882e6b">3bcad65fbf6</span><time datetime="2023-10-05T15:24:54+00:00" title="2023-10-05 15:24:54 +0000">2023-10-05</time></p>
<header class="topbar"><details class="switcher"><summary>master</summary><div class="menu"><strong>branches</strong><a class="current" href="/fork/rust/ref/master/">master</a><strong>tags</strong><a href="/fork/rust/ref/1.39.0/">1.39.0</a><a href="/fork/rust/ref/1.40.0/">1.40.0</a><a href="/fork/rust/ref/1.41.0/">1.41.0</a><a href="/fork/rust/ref/1.41.1/">1.41.1</a><a href="/fork/rust/ref/1.42.0/">1.42.0</a><a href="/fork/rust/ref/1.43.0/">1.43.0</a><a href="/fork/rust/ref/1.43.1/">1.43.1</a><a href="/fork/rust/ref/1.44.0/">1.44.0</a><a class="all" href="/fork/rust/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/rust/">rust</a> / <a href="/fork/rust/ref/master/tree/src/">src</a> / <a href="/fork/rust/ref/master/tree/src/tools/">tools</a> / <a href="/fork/rust/ref/master/tree/src/tools/rust-analyzer/">rust-analyzer</a> / <a href="/fork/rust/ref/master/tree/src/tools/rust-analyzer/docs/">docs</a> / <a href="/fork/rust/ref/master/tree/src/tools/rust-analyzer/docs/dev/">dev</a> / <span class="cur">debugging.md</span></nav>
<span class="view-stats"><span>3.6 KiB</span><span>99 lines</span></span><span class="actions"><a class="raw" href="/fork/rust/raw/48caec1d8fa6ee1b5c45e384be48e661c3efe6e4/src/tools/rust-analyzer/docs/dev/debugging.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><h1>Debugging VSCode plugin and the language server</h1>
<h2>Prerequisites</h2>
<ul>
<li>
<p>Install <a href="https://lldb.llvm.org/">LLDB</a> and the <a href="https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb">LLDB Extension</a>.</p>
</li>
<li>
<p>Open the root folder in VSCode. Here you can access the preconfigured debug setups.</p>
&lt;img height=150px src="https://user-images.githubusercontent.com/36276403/74611090-92ec5380-5101-11ea-8a41-598f51f3f3e3.png" alt="Debug options view"&gt;
</li>
<li>
<p>Install all TypeScript dependencies</p>
<pre class="language-bash"><a-f>cd</a-f> editors/code
<a-f>npm</a-f> ci</pre>
</li>
</ul>
<h2>Common knowledge</h2>
<ul>
<li>All debug configurations open a new <code>[Extension Development Host]</code> VSCode instance
where <strong>only</strong> the <code>rust-analyzer</code> extension being debugged is enabled.</li>
<li>To activate the extension you need to open any Rust project folder in <code>[Extension Development Host]</code>.</li>
</ul>
<h2>Debug TypeScript VSCode extension</h2>
<ul>
<li><code>Run Installed Extension</code> - runs the extension with the globally installed <code>rust-analyzer</code> binary.</li>
<li><code>Run Extension (Debug Build)</code> - runs extension with the locally built LSP server (<code>target/debug/rust-analyzer</code>).</li>
</ul>
<p>TypeScript debugging is configured to watch your source edits and recompile.
To apply changes to an already running debug process, press &lt;kbd&gt;Ctrl+Shift+P&lt;/kbd&gt; and run the following command in your <code>[Extension Development Host]</code></p>
<pre>&gt; Developer: Reload Window
</pre>
<h2>Debug Rust LSP server</h2>
<ul>
<li>
<p>When attaching a debugger to an already running <code>rust-analyzer</code> server on Linux you might need to enable <code>ptrace</code> for unrelated processes by running:</p>
<pre>echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
</pre>
</li>
<li>
<p>By default, the LSP server is built without debug information. To enable it, you'll need to change <code>Cargo.toml</code>:</p>
<pre class="language-toml">  <a-p>[</a-p><a-pr>profile</a-pr><a-p>.</a-p><a-pr>dev</a-pr><a-p>]</a-p>
  <a-pr>debug</a-pr> <a-o>=</a-o> <a-n>2</a-n></pre>
</li>
<li>
<p>Select <code>Run Extension (Debug Build)</code> to run your locally built <code>target/debug/rust-analyzer</code>.</p>
</li>
<li>
<p>In the original VSCode window once again select the <code>Attach To Server</code> debug configuration.</p>
</li>
<li>
<p>A list of running processes should appear. Select the <code>rust-analyzer</code> from this repo.</p>
</li>
<li>
<p>Navigate to <code>crates/rust-analyzer/src/main_loop.rs</code> and add a breakpoint to the <code>on_request</code> function.</p>
</li>
<li>
<p>Go back to the <code>[Extension Development Host]</code> instance and hover over a Rust variable and your breakpoint should hit.</p>
</li>
</ul>
<p>If you need to debug the server from the very beginning, including its initialization code, you can use the <code>--wait-dbg</code> command line argument or <code>RA_WAIT_DBG</code> environment variable. The server will spin at the beginning of the <code>try_main</code> function (see <code>crates\rust-analyzer\src\bin\main.rs</code>)</p>
<pre class="language-rust">    <a-k>let</a-k> <a-k>mut</a-k> d = <a-co>4</a-co><a-p>;</a-p>
    <a-k>while</a-k> d == <a-co>4</a-co> <a-p>{</a-p> <a-c>// set a breakpoint here and change the value</a-c>
        d = <a-co>4</a-co><a-p>;</a-p>
    <a-p>}</a-p></pre>
<p>However for this to work, you will need to enable debug_assertions in your build</p>
<pre class="language-rust"><a-cr>RUSTFLAGS</a-cr>=<a-o>&#39;</a-o>--cfg debug_assertions<a-o>&#39;</a-o> cargo build --release</pre>
<h2>Demo</h2>
<ul>
<li><a href="https://www.youtube.com/watch?v=T-hvpK6s4wM">Debugging TypeScript VScode extension</a>.</li>
<li><a href="https://www.youtube.com/watch?v=EaNb5rg4E0M">Debugging Rust LSP server</a>.</li>
</ul>
<h2>Troubleshooting</h2>
<h3>Can't find the <code>rust-analyzer</code> process</h3>
<p>It could be a case of just jumping the gun.</p>
<p>The <code>rust-analyzer</code> is only started once the <code>onLanguage:rust</code> activation.</p>
<p>Make sure you open a rust file in the <code>[Extension Development Host]</code> and try again.</p>
<h3>Can't connect to <code>rust-analyzer</code></h3>
<p>Make sure you have run <code>echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope</code>.</p>
<p>By default this should reset back to 1 every time you log in.</p>
<h3>Breakpoints are never being hit</h3>
<p>Check your version of <code>lldb</code>. If it's version 6 and lower, use the <code>classic</code> adapter type.
It's <code>lldb.adapterType</code> in settings file.</p>
<p>If you're running <code>lldb</code> version 7, change the lldb adapter type to <code>bundled</code> or <code>native</code>.</p>
</section><div class="code-panel"><pre class="code src" data-hl="src/tools/rust-analyzer/docs/dev/debugging.md"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text"># Debugging VSCode plugin and the language server</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">## Prerequisites</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">- Install [LLDB](https://lldb.llvm.org/) and the [LLDB Extension](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">- Open the root folder in VSCode. Here you can access the preconfigured debug setups.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L8" href="#L8">8</a><span class="code-text">  &lt;img height=150px src=&quot;https://user-images.githubusercontent.com/36276403/74611090-92ec5380-5101-11ea-8a41-598f51f3f3e3.png&quot; alt=&quot;Debug options view&quot;&gt;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L9" href="#L9">9</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L10" href="#L10">10</a><span class="code-text">- Install all TypeScript dependencies</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L11" href="#L11">11</a><span class="code-text">  ```bash</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L12" href="#L12">12</a><span class="code-text">  cd editors/code</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L13" href="#L13">13</a><span class="code-text">  npm ci</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L14" href="#L14">14</a><span class="code-text">  ```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L15" href="#L15">15</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L16" href="#L16">16</a><span class="code-text">## Common knowledge</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L17" href="#L17">17</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L18" href="#L18">18</a><span class="code-text">* All debug configurations open a new `[Extension Development Host]` VSCode instance</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L19" href="#L19">19</a><span class="code-text">where **only** the `rust-analyzer` extension being debugged is enabled.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L20" href="#L20">20</a><span class="code-text">* To activate the extension you need to open any Rust project folder in `[Extension Development Host]`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L21" href="#L21">21</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L22" href="#L22">22</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L23" href="#L23">23</a><span class="code-text">## Debug TypeScript VSCode extension</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L24" href="#L24">24</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L25" href="#L25">25</a><span class="code-text">- `Run Installed Extension` - runs the extension with the globally installed `rust-analyzer` binary.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L26" href="#L26">26</a><span class="code-text">- `Run Extension (Debug Build)` - runs extension with the locally built LSP server (`target/debug/rust-analyzer`).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L27" href="#L27">27</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L28" href="#L28">28</a><span class="code-text">TypeScript debugging is configured to watch your source edits and recompile.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L29" href="#L29">29</a><span class="code-text">To apply changes to an already running debug process, press &lt;kbd&gt;Ctrl+Shift+P&lt;/kbd&gt; and run the following command in your `[Extension Development Host]`</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L30" href="#L30">30</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L31" href="#L31">31</a><span class="code-text">```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L32" href="#L32">32</a><span class="code-text">&gt; Developer: Reload Window</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L33" href="#L33">33</a><span class="code-text">```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L34" href="#L34">34</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L35" href="#L35">35</a><span class="code-text">## Debug Rust LSP server</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L36" href="#L36">36</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L37" href="#L37">37</a><span class="code-text">- When attaching a debugger to an already running `rust-analyzer` server on Linux you might need to enable `ptrace` for unrelated processes by running:</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L38" href="#L38">38</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L39" href="#L39">39</a><span class="code-text">  ```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L40" href="#L40">40</a><span class="code-text">  echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L41" href="#L41">41</a><span class="code-text">  ```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L42" href="#L42">42</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L43" href="#L43">43</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L44" href="#L44">44</a><span class="code-text">- By default, the LSP server is built without debug information. To enable it, you'll need to change `Cargo.toml`:</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L45" href="#L45">45</a><span class="code-text">  ```toml</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L46" href="#L46">46</a><span class="code-text">    [profile.dev]</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L47" href="#L47">47</a><span class="code-text">    debug = 2</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L48" href="#L48">48</a><span class="code-text">  ```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L49" href="#L49">49</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L50" href="#L50">50</a><span class="code-text">- Select `Run Extension (Debug Build)` to run your locally built `target/debug/rust-analyzer`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L51" href="#L51">51</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L52" href="#L52">52</a><span class="code-text">- In the original VSCode window once again select the `Attach To Server` debug configuration.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L53" href="#L53">53</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L54" href="#L54">54</a><span class="code-text">- A list of running processes should appear. Select the `rust-analyzer` from this repo.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L55" href="#L55">55</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L56" href="#L56">56</a><span class="code-text">- Navigate to `crates/rust-analyzer/src/main_loop.rs` and add a breakpoint to the `on_request` function.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L57" href="#L57">57</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L58" href="#L58">58</a><span class="code-text">- Go back to the `[Extension Development Host]` instance and hover over a Rust variable and your breakpoint should hit.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L59" href="#L59">59</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L60" href="#L60">60</a><span class="code-text">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`)</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L61" href="#L61">61</a><span class="code-text">```rust</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L62" href="#L62">62</a><span class="code-text">    let mut d = 4;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L63" href="#L63">63</a><span class="code-text">    while d == 4 { // set a breakpoint here and change the value</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L64" href="#L64">64</a><span class="code-text">        d = 4;</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L65" href="#L65">65</a><span class="code-text">    }</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L66" href="#L66">66</a><span class="code-text">```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L67" href="#L67">67</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L68" href="#L68">68</a><span class="code-text">However for this to work, you will need to enable debug_assertions in your build</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L69" href="#L69">69</a><span class="code-text">```rust</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L70" href="#L70">70</a><span class="code-text">RUSTFLAGS='--cfg debug_assertions' cargo build --release</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L71" href="#L71">71</a><span class="code-text">```</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L72" href="#L72">72</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L73" href="#L73">73</a><span class="code-text">## Demo</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L74" href="#L74">74</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L75" href="#L75">75</a><span class="code-text">- [Debugging TypeScript VScode extension](https://www.youtube.com/watch?v=T-hvpK6s4wM).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L76" href="#L76">76</a><span class="code-text">- [Debugging Rust LSP server](https://www.youtube.com/watch?v=EaNb5rg4E0M).</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L77" href="#L77">77</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L78" href="#L78">78</a><span class="code-text">## Troubleshooting</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L79" href="#L79">79</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L80" href="#L80">80</a><span class="code-text">### Can't find the `rust-analyzer` process</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L81" href="#L81">81</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L82" href="#L82">82</a><span class="code-text">It could be a case of just jumping the gun.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L83" href="#L83">83</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L84" href="#L84">84</a><span class="code-text">The `rust-analyzer` is only started once the `onLanguage:rust` activation.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L85" href="#L85">85</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L86" href="#L86">86</a><span class="code-text">Make sure you open a rust file in the `[Extension Development Host]` and try again.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L87" href="#L87">87</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L88" href="#L88">88</a><span class="code-text">### Can't connect to `rust-analyzer`</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L89" href="#L89">89</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L90" href="#L90">90</a><span class="code-text">Make sure you have run `echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L91" href="#L91">91</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L92" href="#L92">92</a><span class="code-text">By default this should reset back to 1 every time you log in.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L93" href="#L93">93</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L94" href="#L94">94</a><span class="code-text">### Breakpoints are never being hit</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L95" href="#L95">95</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L96" href="#L96">96</a><span class="code-text">Check your version of `lldb`. If it's version 6 and lower, use the `classic` adapter type.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L97" href="#L97">97</a><span class="code-text">It's `lldb.adapterType` in settings file.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L98" href="#L98">98</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L99" href="#L99">99</a><span class="code-text">If you're running `lldb` version 7, change the lldb adapter type to `bundled` or `native`.</span></span></pre></div></div>
</main>
</body>
</html>
