CodyIT@programming.dev to Programmer Humor@programming.devEnglish · 2 days agoThe biggest mystery known to mankindprogramming.devimagemessage-square43fedilinkarrow-up1731arrow-down116
arrow-up1715arrow-down1imageThe biggest mystery known to mankindprogramming.devCodyIT@programming.dev to Programmer Humor@programming.devEnglish · 2 days agomessage-square43fedilink
minus-squareatopi@piefed.blahaj.zonelinkfedilinkEnglisharrow-up16·1 day agoa while ago, during a game jam, while i was making some of the worst gdscript i have ever seen, i have encountered a bug after adding a print to see the value of a variable, the bug disappeared. Confused, i commented out the line i just added. The bug was still fixed i removed the comment. The bug reappeared
minus-squareWillem@kutsuya.devlinkfedilinkarrow-up2·17 hours agoprinting to a console could enforce a flush, sync thread or other shenanigans. usually setting a breakpoint would have the same effect and gives me the suggestion of a threading issue.
minus-squareatopi@piefed.blahaj.zonelinkfedilinkEnglisharrow-up3·16 hours agothe problem wasnt that the print statement fixed the bug the problem was that even if i removed the print statement and added a comment on that line, the bug would also be fixed
a while ago, during a game jam, while i was making some of the worst gdscript i have ever seen, i have encountered a bug
after adding a print to see the value of a variable, the bug disappeared. Confused, i commented out the line i just added. The bug was still fixed
i removed the comment. The bug reappeared
printing to a console could enforce a flush, sync thread or other shenanigans.
usually setting a breakpoint would have the same effect and gives me the suggestion of a threading issue.
the problem wasnt that the print statement fixed the bug
the problem was that even if i removed the print statement and added a comment on that line, the bug would also be fixed