Lojcs@piefed.social to Programmer Humor@programming.devEnglish · 30 days agoNot againmedia.piefed.socialimagemessage-square14fedilinkarrow-up1267arrow-down11
arrow-up1266arrow-down1imageNot againmedia.piefed.socialLojcs@piefed.social to Programmer Humor@programming.devEnglish · 30 days agomessage-square14fedilink
minus-squarememe_historian@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up56·edit-230 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-squareLojcs@piefed.socialOPlinkfedilinkEnglisharrow-up24·edit-230 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·30 days agoAKA heisenbug. Observing it changes the outcome.
minus-squareMatty_r@programming.devlinkfedilinkarrow-up2·27 days 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…