Quote:
Originally Posted by knc1
gdb?
Heard of it, but have never used it.
(Could say that things I write always work, but it would be a lie.)
- - - -
My external 1Tbyte array is trying to recover -
OpenSUSE Tumbleweed is trying to download and install 876 updates -
A rainstorm is making my Internet connection act like a yoyo -
I may just take an early mid-day nap.
|
My debugger of choice has been a ton of ifdef-wrapped printf's scattered through the code (removed before the "production" release). I just set some flags in order to "verbose" (or breakpoint) a selected chunk of code. But sometimes instead of ifdefs I use live code to check argv[] "debug" switches, in more "dynamic" debugging cases.
Although I have single-stepped device drivers with an appropriate softICE -- and I have also attached hardare logic anaylzers to hardware to assist with finding archane software timing glitches. But usually? Printf is my debugger of choice. A "real" debugger just gets in the way for the sort of things I like to do...