Having tried a few things I’m puzzled.
I’m using VSCodium on Linux and was originally set up with the native debugger ennabled (which includes LLDB) and had added the rust-lang extention which includes support for build tasks and the docs say:
Rust support is powered by a separate language server - either by the official Rust Language Server (RLS) or rust-analyzer, depending on the user’s preference. If you don’t have it installed, the extension will install it for you (with permission).
I thought I had rust-analyzer installed because I wasn’t prompted for it, but it isn’t in my extensions list so I’ve been trying to install it as an extension but it doesn’t show up (instructions here don’t work - they just paste a search into the extensions list which doesn’t find rust-analyzer). So I don’t think it is in the market place.
This may explain why I don’t get an option to debug unless I create a launch.config, but when I do that (just tried using safe-vault) I can run the debugger but get the result above (debug toolbar appears for a second and then disappears).
So I’m puzzled as to how VS Codium is supposed to be set up (seems you guys are using an extension I can’t install. Maybe superceded by the rust-lang extension which I can’t get to work.
I don’t think save_vault is being run, and if I mess with the config (e.g. change the name of the executable to safe_NOTHING) the behaviour doesn’t change. I can set a breakpoint in safe_vault.js but it has no effect.
Looking in VSC settings I had RLS selected, so I switched to rust-analyzer. No difference!
Seems like this might be the magic needed:
sudo apt-get install lldb
I’ve not seen any instructions to do that!
VS Codium has now prompted me to install rust-analyzer, so fingers crossed.
BINGO! That’s the missing step, installing lldb