rust-lang / rust-lang/rust-analyzer
RA 0.3.2029 doesn't respect breakpoints
Open
Nobody has claimed this yet.
A-vscode
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hi,
RA 0.3.2020 respects the breakpoints but not the 2029 version when running Debug with from inlay in test module.
mod test {
#[test]
fn test_ra() {
println!("OK");
println!("OK");
}
}
A breakpoint to any statement won't stop.
VScode
Version: 1.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:52:41.959Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.9.7-amd64
active toolchain
----------------
nightly-x86_64-unknown-linux-gnu (default)
rustc 1.81.0-nightly (d7f6ebace 2024-06-16)
Stepping down to 2020 solves the issue. Any new option to be aware of ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are identified. Start by reproducing the breakpoint failure in the listed VS Code 1.91.0 and nightly Rust environment, then compare rust-analyzer 0.3.2020 with 0.3.2029; done means breakpoints stop on statements in the test module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100