3 ms·
Because they didn't handle an integer timer wrapping around correctly. That answers most of the question. What remains is did they forget altogether or program
by usr1106 7y ago
Because they didn't handle an integer timer wrapping around correctly. That answers most of the question. What remains is did they forget altogether or program it incorrectly. I'd say I have seen worse click bait, this post didn't annoy me even if the analysis was much simpler than a Google project zero blog post.
Did you seriously expect to see Windows source code published? AFAIK it is still under strict NDA regardless of how old it is or did I miss some headlines?
- ggambetta 7y agoI've read several blog posts that actually go and analyze why a bug happens, by disassembling DLLs or whatever they need to do. So yes, with a title like that, I do expect more than "oh, it's probably related to integer overflow somehow."