This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 156
Debugging not running through hover menu or Debuggables command #380
Comments
Ok so I managed to make it work by editing |
Hey ,
I have not tested neotest on rust yet. rust-tools debuggables show up . and this is my rust-tools setup
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No matter if I try to debug a test or a binary, tests seem to never really launch, I don't seem to have any output related to debugging whatsoever. My terminal does not split either.
When I launch a binary without debugging, I do have a split that shows the output of both the build and the execution though.
If I launch a Debuggable I just have the following output without anything else happening :
Debugger never seem to launch, whether I put a breakpoint in the test or not.
I, however, manage to debug my main binary by calling
require("dap").continue()
, using breakpoints and watches.I use CodeLLDB as my debugger and the part of the configuration related to the DAP looks like this :
I tried to change
codelldb_path
to some dumb value to see if I not messed up my paths obviously, and even though nothing change in the behavior I observed, I kinda ruled it out after triple checking :Even though it seems kind of irrelevant (unless... ?), here are my DAP configurations for Rust. I tried to just remove them, thinking that could override the ones rust-tools use internally, but it didn't change anything apparently :
Could someone explain to me the dumb thing I missed/the mistake(s) I made in my attempts to make debugging through rust-tools work, please ? 😬
Thanks in advance !!
The text was updated successfully, but these errors were encountered: