3 ms·
Debuggers help to isolate _where_ code breaks as much as what state it was in when it broke. Seeing that fn1 breaks on DataB is not as useful as seeing that fn
by maerF0x0 8y ago
Debuggers help to isolate _where_ code breaks as much as what state it was in when it broke.
Seeing that fn1 breaks on DataB is not as useful as seeing that fn1(f2(DataA)) is the actual error.
- sushisource 8y agoYes, this is why they are useful. Generally speaking once I've found where the error is, it's real simple to find the one or two variables in scope, look at their values, and figure out the bug. I would agree that if you're using a debugger to verify over many iterations that something isn't going wacky with state, then yeah, that's not a great sign.