The code worked differently when the moon was full
The code worked differently when the moon was full
I love a good bug, especially ones that are initially hard to explain but then ...
![The code worked differently when the moon was full](https://programming.dev/pictrs/image/f29e3c3f-5152-470b-a700-58dff6f8ad80.jpeg?format=webp&thumbnail=256)
"We can't send mail farther than 500 miles from here..."
40 0 ReplyI love these stories! There's also,
And now that I've gone searching for these I see that they've all been helpfully collected on http://beza1e1.tuxen.de/lore/index.html
15 0 ReplyThose are great stories, thanks for sharing!
5 0 Reply
tldr: the code worked differently when a signed version of gettickcount was negative, giving a change that repeats over 49.7 days
34 0 ReplyThe moon phase cycle is 29.5 days. The reported bug cycle is 49 days. Yet somehow, "Not strictly the cycle of the moon but close".
With that sort of logical analysis ability, no wonder this guy struggles with stupid bugs.
6 1 ReplyThat code has a werewolf in it!
4 0 Replyimpure functions and their consequences
2 0 Reply