Lojcs@piefed.social to Programmer Humor@programming.devEnglish · 6 days agoNot againmedia.piefed.socialimagemessage-square13linkfedilinkarrow-up1269arrow-down11
arrow-up1268arrow-down1imageNot againmedia.piefed.socialLojcs@piefed.social to Programmer Humor@programming.devEnglish · 6 days agomessage-square13linkfedilink
minus-squarememe_historian@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up54·6 days 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-squareMatty_r@programming.devlinkfedilinkarrow-up2·4 days agoWhen adding a debug print statement changes the locking of a thread and the problem doesn’t occur…
minus-squareLojcs@piefed.socialOPlinkfedilinkEnglisharrow-up24·6 days 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-up19·6 days agoAKA heisenbug. Observing it changes the outcome.
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 💀
When adding a debug print statement changes the locking of a thread and the problem doesn’t occur…
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.