Lojcs@piefed.social to Programmer Humor@programming.devEnglish · 4 days agoNot againmedia.piefed.socialimagemessage-square13fedilinkarrow-up1264
arrow-up1264imageNot againmedia.piefed.socialLojcs@piefed.social to Programmer Humor@programming.devEnglish · 4 days agomessage-square13fedilink
minus-squarememe_historian@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up52·edit-24 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·1 day agoWhen adding a debug print statement changes the locking of a thread and the problem doesn’t occur…
minus-squarebandwidthcrisis@lemmy.worldlinkfedilinkarrow-up19·4 days agoAKA heisenbug. Observing it changes the outcome.
minus-squareLojcs@piefed.socialOPlinkfedilinkEnglisharrow-up23·edit-24 days agoOr something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or
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…
AKA heisenbug.
Observing it changes the outcome.
Or something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or