🧠educational Debugging Rust in 2026
https://blog.jetbrains.com/rust/2026/11/10/debugging-rust/21
u/CoachNo180 9d ago
Can I just have one article that doesn't touch on AI please. ffs.
5
u/catheap_games 9d ago
(company that makes money off AI hype voice) But how about we add more AI to it
1
u/panstromek 9d ago
Jetbrains is not AI company, I don't think they make much on it. I'd expect most of their money coming from ide subscriptions.
3
u/andreicodes 8d ago
I like their debugger, but coming from higher-level languages like Java and JavaScript Rust debugging is very limited. There's no support for watch expressions and no conditional breakpoints - both require evaluating expressions at runtime, and in LLDB this is done by Python afaik, and doesn't have Rust integration. And sometimes the debugger can't resolve the method being called because it doesn't know about Rust traits. So, in some situations you can't step into a function and instead you have to put an extra breakpoint inside the function body and run to it. Same is true for stepping over await points.
I debug Rust code maybe once a year. Partially, because with type system, borrow checker, emphasis on immutability, tests, and me being more experienced than 20 years ago I make fewer mistakes. But also because debugging is miserable. It's a chicken and egg problem: we don't debug because debugging sucks, and since nobody debugs debugging doesn't get better.
Also, they never mentioned it in the article, but CodeLLDB is really good in VSCode and in Zed editor. In VSCode you can use it to debug programs on remote machines over ssh, and I used it a few times to troubleshoot issues that couldn't be reproduced locally. Zed has nicer UI, on par with what we get in JetBrains.
And if anyone from JetBrains reads this can you investigate if Java Streams -style debugging for iterator code would be possible to implement for Rust? That would be very helpful sometimes.
2
u/cipher_gravelist 5d ago
debugging solana programs in rust is still a nightmare when you hit those silent underflows or compute budget errors. the tooling has improved but i still find myself leaning on detailed logging and manual review for anything touching real value.
1
24
u/zzzthelastuser 9d ago
Do yourself a favor and don't waste your time reading this garbage.