3 ms·
> For debugging it mostly relates to chopping up the program in to bits that are 'verified good' and 'unsure', until you are literally staring at the bug. It s
by varjag 16y ago
> For debugging it mostly relates to chopping up the program in to bits that are 'verified good' and 'unsure', until you are literally staring at the bug.
It should be noted there's a whole class of bugs where divide and conquer simply doesn't work. E.g. about anything with race condition.
Good points otherwise.
- jacquesm 16y agoTrue enough, and interrupt driven programs tend to exhibit very nasty ones as well where that strategy does not work. It's not a 100% silver bullet but it will get you quite far.
- deleted 16y ago[deleted]
- deleted 16y ago[deleted]