– This is Cranelift’s debug tracking issue.Tracking Issues (things to keep an eye on): Personally, what would be amazing is if the Rust Analyzer VSCode extension could eventually hook into Cranelift for debugging in the future to make life as easy as possible. I think this is the way forward, especially as LLDB will only get us so far One of the outcomes from this is better handling of Rust variables during debug builds and not optimizing away everything. There is an initiative to move debug builds to run on Cranelift. Remember, you do get a bit more info using LLDB so consider using that.

I’m sure you’ve seen this, it can be quite frustrating. Variable is optimized away and not available. If you don’t already have a launch.json file you can create one by opening up your menu ( Ctrl +shift + p / cmd + shift + p) selecting “Debug: Open launch.json” and select C++ or lldb.īelow is the current configuration from Boa, you can copy and paste this and re-use for your own project. It is now available on the VSCode Marketplace Configure VSCode If you’ve heard of RLS then Rust Analyzer is a replacement for that (often dubbed RLS 2.0). It has excellent IDE support for Rust and is being actively developed.

Regardless of which OS you use I recommend getting Rust Analyzer (RA). Windows users can also use the C/C++ Extension instead if they prefer but for the benefit of this, we will choose CodeLLDB. If you’re on MacOS, Linux or Windows then CodeLLDB. You may also need to run rustup component add rust-src if you wish to step into standard library components (mentioned below). You can grab Visual Studio Code from here The best way to install Rust is via Rustup Its been a while since I’ve posted about debugging rust, we’ve come a long way since 2017 and I wanted to do an update on getting set up for Rust Debugging.

Visual studio code debugger config c++