> 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, b

> 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.