Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with timer wrap around #2

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments
Open

Issue with timer wrap around #2

GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

How can the problem happen:
1. current time = 0xFFFF0000
2. timer should expire at 0xFFFFFFF8
3. the counter expires at 0xFFFFFFF8, but by the time the software is
reading the current time, it has rolled over to 0x00000002 and when it
compare that value to the timer expiration date, it concludes it has not
yet expired

The goal is not to miss and timer in the list.  Unfortunately this scenario
can happen.



Original issue reported on code.google.com by [email protected] on 11 Jan 2010 at 2:12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant