@sellingspams@feddit.de to Programmer Humor@lemmy.ml • 2 years ago6 stages of debuggingi.imgur.comimagemessage-square29fedilinkarrow-up1469arrow-down14cross-posted to: hdev@lemmy.world
arrow-up1465arrow-down1image6 stages of debuggingi.imgur.com@sellingspams@feddit.de to Programmer Humor@lemmy.ml • 2 years agomessage-square29fedilinkcross-posted to: hdev@lemmy.world
minus-square@zqwzzle@lemmy.calinkfedilinkEnglish11•2 years agoAnd then the logging fixes the subtle timing issue causing the problem.
minus-squaresickmatterlinkfedilink1•2 years agoEspecially if logging ends up spreading a global mutex around the log file.
minus-square@danc4498@lemmy.worldlinkfedilink7•2 years agoWe have logging software built in, but I can never remember how to turn it on, so I just console.log
minus-square@0x4E4F@sh.itjust.workslinkfedilink4•edit-22 years 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”