VsCode Debug RUST

Brian Horakh — Mon, 23 May 2022 01:47:34 +0000

This guide is intended to explain how to use the VSCode LLDB debugger with RUST.

Cunningham's Law states "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer." The concept is named after Ward Cunningham, the inventor of wiki software.

With the Cunningham spirit in mind, if you know a better way to do this, or other cool stuff I should try please let me know in the comments.

Resources I used:

CodeLLDB natively supports visualization of most common Rust data types:

Built-in types: tuples, enums, arrays, array and string slices.
Standard library types: Vec, String, CString, OSString, Path, Cell, Rc, Arc and more.

Below is a fully functioning launch.json for vscode that works with rust 1.60, inline comments:

{
    "version": "0.2.0",
    "configurations": [
        {
            // 😓 LLDB Help: https://github.com/vadimcn/vscode-lldb/discussions
            "type": "lldb",
            "request": "launch",
            "name": "Debug",

            // 🤓 use this to debug RUST binaries:
            "program": "${workspaceRoot}/target/debug/${workspaceRootFolderName}",

            // 🤓 use cargo for libraries
            /* 
            "cargo": {
                "args": ["test", "--no-run", "--lib"], // Cargo command line to build the debug target
                // "args": ["build", "--bin=foo"] is another possibility
                "filter": { // Filter applied to compilation artifacts (optional)
                    "name": "mylib",
                    "kind": "lib"
                }            
            */
            "args": [],
            "cwd": "${workspaceFolder}",
            "sourceLanguages": ["rust"], // required to add support for Vec, String, enum .. 
            "terminal":"integrated",        // can also be 'console', 'external'

            // 🤓 https://github.com/vadimcn/vscode-lldb/blob/master/MANUAL.md#stdio
            "stdio": null                // connect all streams to default terminal, can also use file(s)

            // "stopOnEntry":true,          // should open an lldb hex/asm dump on start
        ]
}

_b00t_ - a startup environment

Brian Horakh — Tue, 11 May 2021 08:47:40 +0000

The idea behind b00t is a framework to build a startup properly and provide tooling & infrastructure, devops pipeline, vs code environments, "startup kit", mostly python & typescript with optional libraries such as ai, crypto, ecommerce, etc. necessary for building and testing and deploying those.

I'm still very early into the process, I'm presently building heavily into the Azure Cloud, OpenID and the authentication middleware in Vue.JS, using the Vittesse framework. The final product can give you a Vue.JS interface to push a button that runs an authenticated function, and then builds a plurality of messaging layers MQTT, Redis, etc. At least that's the dream.

Presently the docker and fzf menuing system is coming along nicely. This is a massive cloud-stack span of knowledge will ultimately come together in a crescendo of pre-configured bash scripting & menuing environment, thereby compressing the first 100 hours of action required for "creating a startup" into a few commands and reducing operational costs substantially by starting from a functional template.

http://github.com/elasticdotventures/_b00t_

DEV Community: Brian Horakh

VsCode Debug RUST

Resources I used:

_b00t_ - a startup environment