@[email protected] to Programmer [email protected] • 1 year ago6 stages of debuggingi.imgur.comimagemessage-square28fedilinkarrow-up1456arrow-down14cross-posted to: [email protected]
arrow-up1452arrow-down1image6 stages of debuggingi.imgur.com@[email protected] to Programmer [email protected] • 1 year agomessage-square28fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilinkEnglish13•1 year agoAnd then the logging fixes the subtle timing issue causing the problem.
minus-squaresickmatterlinkfedilink1•1 year agoEspecially if logging ends up spreading a global mutex around the log file.
minus-square@[email protected]linkfedilink7•1 year agoWe have logging software built in, but I can never remember how to turn it on, so I just console.log
minus-square@[email protected]linkfedilink5•edit-21 year agoStep 4.6: Get another drive for the logs.
Stage 4.5: console.log() everything.
And then the logging fixes the subtle timing issue causing the problem.
Race conditions are the worst
Good ol’ Heisenbugs.
Especially if logging ends up spreading a global mutex around the log file.
We have logging software built in, but I can never remember how to turn it on, so I just console.log
Step 4.6: Get another drive for the logs.
“Oh…that’s why it’s not working”