Lojcs@piefed.social to Programmer Humor@programming.devEnglish · 3 months agoNot againmedia.piefed.socialimagemessage-square14linkfedilinkarrow-up1258arrow-down11
arrow-up1257arrow-down1imageNot againmedia.piefed.socialLojcs@piefed.social to Programmer Humor@programming.devEnglish · 3 months agomessage-square14linkfedilink
minus-squarememe_historian@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up55·3 months agoIt’s a race condition that doesn’t get triggered when you run the program through a debugger or with copious amounts of debug log output 💀
minus-squareLojcs@piefed.socialOPlinkfedilinkEnglisharrow-up23·3 months agoOr something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or
minus-squarebandwidthcrisis@lemmy.worldlinkfedilinkarrow-up18·3 months agoAKA heisenbug. Observing it changes the outcome.
minus-squareMatty_r@programming.devlinkfedilinkarrow-up2·3 months agoWhen adding a debug print statement changes the locking of a thread and the problem doesn’t occur…
It’s a race condition that doesn’t get triggered when you run the program through a debugger or with copious amounts of debug log output 💀
Or something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or
AKA heisenbug.
Observing it changes the outcome.
When adding a debug print statement changes the locking of a thread and the problem doesn’t occur…