sellingspams@feddit.de to Programmer Humor@lemmy.ml · 2 年前6 stages of debuggingi.imgur.comimagemessage-square28linkfedilinkarrow-up1458arrow-down14cross-posted to: [email protected]
arrow-up1454arrow-down1image6 stages of debuggingi.imgur.comsellingspams@feddit.de to Programmer Humor@lemmy.ml · 2 年前message-square28linkfedilinkcross-posted to: [email protected]
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up13·2 年前And then the logging fixes the subtle timing issue causing the problem.
minus-squaresickmatter@fedia.iolinkfedilinkarrow-up1·2 年前Especially if logging ends up spreading a global mutex around the log file.
minus-squaredanc4498@lemmy.worldlinkfedilinkarrow-up7·2 年前We 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 年前Step 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”