News for hackers. Stuff that matters.
Re:Speeding up the Rust edit-build-run cycle by flohofwoe on Friday November 15, 2024 @03:11AM (#42144852)
> much more so than what I've seen from C/C++/Rust debuggers.

...have you ever used the Visual Studio integrated debugger for C/C++ instead of 'raw' gdb/lldb without a UI frontend?

Re:Speeding up the Rust edit-build-run cycle by kaba0 on Friday November 15, 2024 @03:32AM (#42144950)
I mean, even then c/CPP will optimize out stuff and you won't get as nice one-to-one mapping as you do with eg. Java.
Re:Speeding up the Rust edit-build-run cycle by flohofwoe on Friday November 15, 2024 @03:43AM (#42145010)
That's why the debug build config one uses during development only does little to no optimizations.
Re:Speeding up the Rust edit-build-run cycle by kaba0 on Friday November 15, 2024 @03:47AM (#42145038)
My point is that even that little can sometimes lead to less pleasant experiences, like stepping half a function's body ahead.
Re:Speeding up the Rust edit-build-run cycle by flohofwoe on Friday November 15, 2024 @03:58AM (#42145100)
Hmm, I've only seen that in some 'new-ish' languages sometimes (like currently Zig), which I think is a compiler bug when generating debug info. In C/C++ I see such random stepping only when trying to debug an optimized program.