News for hackers. Stuff that matters.
Re:I do not use a debugger by nickpsecurity on Tuesday June 21, 2016 @03:25PM (#11948682)
The links actually had the counterpoints I was going to make: hardware-level issues like device interactions and memory corruption. You're not going to figure those out just looking at source code. You need to see how the live value got inappropriately transformed by something that had no business transforming it. That said, the small counterpoints support the consensus in the links that debuggers could be relegated to a rare tool you break out rather than essential part of development. I'm personally undecided on the issue.

Whereas, I encourage Design-by-Contract interface checks, strong typing, and static analysis over TDD. You can use them in conjunction but you knock out more bugs with the former. Plus encode the assumptions in a simple way. Even better, what you knock out applies to all cases within the spec instead of what specific ones you thought to test.

Re:I do not use a debugger by vardump on Tuesday June 21, 2016 @06:03PM (#11949797)
> hardware-level issues like device interactions and memory corruption. You're not going to figure those out just looking at source code.

Well, that's right, but you can't step through something like a DMA transfer setup or IRQ routine either. By the time you've done first single step, the hardware state is already bad and everything has timed out.

Distributed system interactions are also nearly impossible targets for productive use of a debugger.

In both cases, mostly I just do very verbose logging.