4 ms·
Rusts current pretty printers in lldb and gdb are just not good enough for a fluid step debugging experience. I've had luck with intellij IDE's but it's very sa
by merksoftworks 2y ago
Rusts current pretty printers in lldb and gdb are just not good enough for a fluid step debugging experience. I've had luck with intellij IDE's but it's very sad that the best we can do in a language with such good devex tooling is print debugging.
Theoretically you could generate debug scripts with a macro and embed them with
#![debugger_visualizer(gdb_script_file = "../foo.py")]
but I haven't seen anyone go through the trouble.
- landr0id 2y agoThe pretty printers seem to break from time to time as well with compiler updates: https://www.reddit.com/r/rust/comments/1f28akn/invalid_value_for_elements_in_vec_when_viewed_in/lk4vrpl/?context=3 https://www.reddit.com/r/rust/comments/1f28akn/invalid_value...