Codelldb does not seem to instanciate a panic breakpoint by default in neovim with nvim-dap

[Quessou]

First of all, I'm sorry if I'm asking a question in Codelldb's Q&A section without being sure that the issue comes from here, but I guess I have to start somewhere.

I am trying to get something that is here by default when I debug some Rust code in VSCode : breakpoint automatically toggled on rust_panic.

I tried to look at issues on this repository, I saw that sourceLanguages parameter has to contain the rust value to ensure that this kind of specific things is set properly. I also saw that it seems to be kinda of a default actually, but anyway I added it in my dap configuration like following :

    {
        name = "Launch an executable",
        type = "codelldb",
        request = "launch",
        program = function()
            vim.fn.jobstart('cargo build')
            return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/', 'file')
        end,
        cwd = "${workspaceFolder}",
        stopOnEntry = false,
        showDisassembly = "never",
        sourceLanguages = { "rust" }
    },

But I never hit any breakpoint in case of a panic, even in a very simple case like this one :

fn main() {
    println!("Hello, world!");
    let a: Vec<u32> = vec![];
    println!("{}", a[3]);                   // This panics obviously
    println!("Goodbye, world !");
}

Is this a known pitfall that has some workaround ? Is there another way to tell codelldb that the code it's going to debug is Rust code, and thus, set appropriate exception breakpoints ?
If not, where should I look for a culprit and a solution ?

Anyway, thanks in advance !! Codelldb is an incredible tool ❤️

[vadimcn]

Unfortunately, the DAP protocol is designed such that the adapter must report the set of supported exception breakpoints before it gets the launch request, so this information needs to be specified on the command line when launching the adapter. In VSCode, the editor part of the extension code takes care of that. Since vimspector is not customized for codelldb, it doesn't. If there's a way to specify the debug adapter's command line parameters, you can add --settings '{"sourceLanguages":["rust"]}'