sellingspams@feddit.de to Programmer Humor@lemmy.ml · 1 year ago6 stages of debuggingi.imgur.comimagemessage-square28fedilinkarrow-up1458arrow-down14
arrow-up1454arrow-down1image6 stages of debuggingi.imgur.comsellingspams@feddit.de to Programmer Humor@lemmy.ml · 1 year agomessage-square28fedilink
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up13·1 year agoAnd then the logging fixes the subtle timing issue causing the problem.
minus-squaresickmatter@fedia.iolinkfedilinkarrow-up1·1 year agoEspecially if logging ends up spreading a global mutex around the log file.
minus-squaredanc4498@lemmy.worldlinkfedilinkarrow-up7·1 year agoWe have logging software built in, but I can never remember how to turn it on, so I just console.log
minus-square0x4E4F@sh.itjust.workslinkfedilinkarrow-up5·edit-21 year agoStep 4.6: Get another drive for the logs.
minus-squareSpicyTofuSoup@lemmy.sdf.orglinkfedilinkarrow-up1·1 year ago“Oh…that’s why it’s not working”
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”