-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RA 0.3.2029 doesn't respect breakpoints #17568
Comments
Not aware of any changes, but note that rust-analyzer does not handle debugging Rust code; it only integrates with existing debugging tools. It might be that your code is not being built with debug info. |
You are right but I gelt like to report a change that happened right after the RA update and that disappeared with the downgrade. Maybe someone has an idea of what's going on.. |
There was a change to the debug task here cb523fc which broke some stuff, and another followup in https://github.com/rust-lang/rust-analyzer/blob/master/editors/code/src/debug.ts which fixed things btu this might still have changed some behavior |
Just a side note, I still have the same issue with RA v2037 and codeLLDB, in vscode. Anyone else experience this ? I would like to not be stuck in v2020. |
I think I found the issue on our side |
@Veykril Just installed v2045 and the problem still occurs. |
Thanks for checking again, I'll take another look. What debugging extension are you using? |
@Veykril : many thanks to you. I use codeLLDB. Every extensions are up to date on my system. |
Hmm, breakpoints do work for me on the latest release 😕 |
I will try with a naked vscode and see. I will report in two/three hours. Thanks a lot |
Ok it works on a naked installation. |
@Veykril found the culprit! it's in my setting.json I had:
that launched the optimized version of my code when clicking the "release" inlay button above my test.
which is a differing behavior from v2020. It is as if When removing |
Hi,
RA 0.3.2020 respects the breakpoints but not the 2029 version when running Debug with from inlay in test module.
A breakpoint to any statement won't stop.
VScode
Stepping down to 2020 solves the issue. Any new option to be aware of ?
The text was updated successfully, but these errors were encountered: