2 ms·
Yes, I consider a step-debugger that's tightly integrated with the source editor for a seamless edit-compile-debug loop quite essential for development (not jus
by flohofwoe 5y ago
Yes, I consider a step-debugger that's tightly integrated with the source editor for a seamless edit-compile-debug loop quite essential for development (not just for "actual" debugging). A debugger allows me to explore code (my own and other people's) from the "inside", instead of just observing its behaviour from the "outside". Of course I also use temporary print statements, log messages and various types of tests, those are all just additional tools in the development tool box.
Also, with a good UI debugger there's not much to "learn" since the UI is pretty much self-explanatory. You usually have two or three hotkeys for step-into, step-over and step-out, click with the mouse to set a breakpoint, and a few UI panels to inspect variables and memory. Everything else are advanced features that are useful to know, but not essential.
- nerdponx 5y agoWhat GUI debugger(s) do you use/recommend?
- flohofwoe 5y agoDepends on what platform I'm on and what programming language I'm using, Visual Studio's or Xcode's integrated debuggers for C and C++. Visual Studio Code has debugger plugins for almost everything, but the debugging UI is more bare-bones than (for instance) Visual Studio.