[Spacemacs] Making the Rust (DAP) debugger work?

Hi,
I'm using Spacemacs to work with Rust.
So far, I haven't been able to make the debugger work.

Could someone be so kind as to please point me to any missing thing here?

Things I have done so far:

  1. Added rust to my dotspacemacs-configuration-layers
(rust :variables
        lsp-rust-analyzer-cargo-auto-reload t
        rustic-format-on-save t)
  1. Made sure rust-lldb, lldb, lldb-dap, and lldb-mi are in my path:
% which rust-lldb
/usr/bin/rust-lldb

% which lldb
/usr/bin/lldb

% which lldb-dap
/usr/lib/llvm-19/bin/lldb-dap

% which lldb-mi 
/home/allentiak/opt/bin/lldb-mi
  1. Correctly Installed the relevant VS Code extensions:
% cd ~/.emacs.d/.extension/vscode
% tree -L 2
.
├── codelldb
│   ├── [Content_Types].xml
│   ├── extension
│   └── extension.vsixmanifest
├── firefox-devtools.vscode-firefox-debug
│   ├── [Content_Types].xml
│   ├── extension
│   └── extension.vsixmanifest
├── msjsdiag.debugger-for-chrome
│   ├── [Content_Types].xml
│   ├── extension
│   └── extension.vsixmanifest
├── ms-vscode.node-debug2
│   ├── [Content_Types].xml
│   ├── extension
│   └── extension.vsixmanifest
└── webfreak.debug
    ├── [Content_Types].xml
    ├── extension
    └── extension.vsixmanifest
  1. Tried my setup on a (suppossedly working) sample repo:

Mentioned as a sample repo for the following article:

I took a quick look to see if I can get it working on my Emacs 30.1 but no luck. In the end I ran into problems that looked like "variable/function not defined". I roughly followed this guide: Configuring Emacs for Rust development | Robert Krahn

I personally do not like dap-mode, and I prefer to debug in the terminal with either gdb or lldb. They have TUI modes if you like that. Have you tried this or are you fixated on using dap mode?

Edit: You might also find some help in the issues listed here: GitHub · Where software is built
Edit 2: For a graphical client to GDB you can look at gdbgui. I just checked that it works fine with Rust. All you have to do is load the test binary and then show filesystem > Fetch source files. You can e.g. locate the source file you want, and click on a line number, and it'll put a breakpoint there. It doesn't display too great on my Firefox, probably needs Chrome.