sellingspams@feddit.de to Programmer Humor · 2 years ago6 stages of debuggingi.imgur.comexternal-linkmessage-square35fedilinkarrow-up1647arrow-down15cross-posted to: hdev@lemmy.world
arrow-up1642arrow-down1external-link6 stages of debuggingi.imgur.comsellingspams@feddit.de to Programmer Humor · 2 years agomessage-square35fedilinkcross-posted to: hdev@lemmy.world
minus-squareDonjonMaister@programming.devlinkfedilinkarrow-up29·2 years agoStage 4.5: console.log() everything.
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up16·2 years agoAnd then the logging fixes the subtle timing issue causing the problem.
minus-squaresickmatter@fedia.iolinkfedilinkarrow-up1·2 years agoEspecially if logging ends up spreading a global mutex around the log file.
minus-squaredanc4498@lemmy.worldlinkfedilinkarrow-up7·2 years 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-22 years agoStep 4.6: Get another drive for the logs.
minus-squaregerdesjlinkfedilinkarrow-up1·2 years ago4.7: Write app specific log parser 4.8: Fix log parser goto 0.99999999999999923415
minus-squareSpicyTofuSoup@lemmy.sdf.orglinkfedilinkarrow-up1·2 years 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.
4.7: Write app specific log parser 4.8: Fix log parser goto 0.99999999999999923415
“Oh…that’s why it’s not working”