EatingOnions@lemmy.world to Programmer Humor@lemmy.ml · 3 个月前Why I always keep doing it...lemmy.mlimagemessage-square26linkfedilinkarrow-up1318arrow-down15
arrow-up1313arrow-down1imageWhy I always keep doing it...lemmy.mlEatingOnions@lemmy.world to Programmer Humor@lemmy.ml · 3 个月前message-square26linkfedilink
minus-squareChais@sh.itjust.workslinkfedilinkarrow-up1·3 个月前Well yes, the trick is to attach the debugger for the second run.
minus-squareElvith Ma'for@feddit.orglinkfedilinkarrow-up7·3 个月前…and because it slows down the execution a bit and this avoids the race condition that triggers the bug, it now runs flawlessly.
minus-squareTiredGoose@lemmy.ziplinkfedilinkarrow-up2·3 个月前And the order of Set traversal in the JVM is different so the other bug also doesn’t show up
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up2·3 个月前If the customer isn’t running the same debugger i am, i have no sympathy for them. (I’m joking!)
Well yes, the trick is to attach the debugger for the second run.
…and because it slows down the execution a bit and this avoids the race condition that triggers the bug, it now runs flawlessly.
And the order of Set traversal in the JVM is different so the other bug also doesn’t show up
If the customer isn’t running the same debugger i am, i have no sympathy for them. (I’m joking!)