bug: Rust debugging issue

[tomhampshire]

Did you check docs and existing issues?

• I have read all the LazyVim docs
• I have searched the existing issues of LazyVim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.9.5

Operating system/version

Arch

Describe the bug

After doing a couple of cycles of debugging tests using lazyvim's out-of-the-box configuration of lang.rust ● lang.rust  crates.nvim  nvim-cmp  nvim-lspconfig  nvim-treesitter  rustaceanvim  mason.nvim  neotest it will get to a state whether neither the "Debug nearest" (errors shown in the two errors in the top right of the image) or the "Run nearest" will execute (error shown in the centre of the image). The only way to prevent this from happening is to exit and restart neovim, when everything will work for a short while before the error returns.

I expect this is an issue with one of the other plugins or an incompatibility with my system, but I'm having real trouble providing more information. If anyone can instruct me on producing some other information to troubleshoot with, please let me know. If we identify an issue with a different plugin, I'm happy to create a relevant bug report there.

Steps To Reproduce

1. install the latest lazyvim on NVIM v0.9.5
   Build type: Release
   LuaJIT 2.1.1702233742

2. install the lang.rust extra from LazyExtras

3. install codelldb from Mason

4. install lldb version 17.0.6 from Arch's package manager

5. run the debugger on tests using leader, t, d - then continue or terminate.

6. repeat 5. until the errors occur

This has been reproduced on two separate machines

Expected Behavior

The debugger and test run

Repro

No response