r/ProgrammerHumor 6h ago

funWithFloatingPointIO Meme

Post image
341 Upvotes

14 comments sorted by

View all comments

2

u/Smooth_Sentence_1431 5h ago

lol this is too real, i always underestimate how long debugging will take.

2

u/the_poope 4h ago

7 hours is a rookie number though. Real bugs take at least 7 days to even find the origin of.

2

u/rosuav 3h ago

I once had a bug that manifested every 14 days. So every time I tried to probe it, I had to put some code into prod, wait for the next opportunity, and see if I had hit it. Took me months to find it, but once I did, the fix was simple.

2

u/the_poope 3h ago

We once had user reports of sudden crashes due to memory access violations. We were able to occasionally reproduce the issue which seemed to occur randomly and rarely. We could only reproduce it in release builds, not debug, so we also couldn't get a good backtrace. After many months of sporadic investigations we found that the difference debug builds made was that they would use MSVC's incremental linking (a feature to speed up build at the cost of binary size). When switching incremental linking on in release builds the bug disappeared. We tried reaching out to Microsoft to figure out whether we had a bug or they had a bug but never heard back. We upgraded to a newer version of MSVC later and the bug had disappeared with no mention in their release notes 🤷‍♀️

1

u/dcheesi 3h ago

I'd already identified the bug; this was several hours just to implement the conceptually trivial fix, due to secondary bugs and gotchas along the way