As someone who used to write a ton of C++ and only occasionally fired up gdb (and never anything fancier), I feel like maybe "easily" means different things to different people.
Going by what was said above and how I developed in C++, it sounds like "easily" to me.
Yeah, I always been an IDE guy since Turbo Pascal 5.5 and only reluctantly used vi and Emacs as poor man's IDE replacement.
Rust debugging works beautifully with Xcode. I would assume it works with Linux graphical debugging tools as well.
Visual Studio support is mostly gated on LLVM support for PDB. We do have support for using the MSVC toolchain as of a couple of releases ago, so I'm not actually sure what if anything is left to get that working.
Thanks for the update, I thought it was worse than that given my experience on Windows.
Also many thanks for the MSVC toolchain, that is what I have been using.
Any examples or tutorials? Last time I tried this (which wasn't very long ago), I would only occasionally be able to step across Rust code and Xcode would often crash on me.
I just use Xcode's debugger on Rust code. If you see issues, please file bugs against Rust; I'd like Xcode to work.
Re:Why I'm Choosing C++
by steveklabnik on Monday February 01, 2016 @10:16AM
(#11012153)
I haven't used it yet, but https://github.com/pistondevelopers/visualrust claims to have started MIEngine integration.
Thanks for the heads up.
Re:Why I'm Choosing C++
by forrestthewoods on Monday February 01, 2016 @11:04AM
(#11012521)
Easy means:
* breakpoint debugging * ability to step debugger line by line * high quality watch window
GDB does not qualify as easy. Ability to printf debug, while 100% mandatory, is also not easy.
> Yes.
Easily means using something like Visual Studio debuggers, with its graphical visualizers.
Command line gdb is something I use when there isn't any other option available.