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

timeGetTime breaks the Time class comparison operators after very long machine uptime #234

Open
kgersen opened this issue Jun 7, 2017 · 1 comment
Assignees
Projects
Milestone

Comments

@kgersen
Copy link
Owner

kgersen commented Jun 7, 2017

see : https://www.freeallegiance.org/forums/index.php?s=&showtopic=68187&view=findpost&p=700567

possible solutions:

  • add a check at start and warn user to reboot his computer if uptime >24 days for instance
  • get a timeGetTime reference when program starts and use it as a '0' for every call to timeGetTime
  • use c++11 chrono lib
@kgersen kgersen added this to the Summer 2017 milestone Jun 7, 2017
@kgersen kgersen self-assigned this Jun 7, 2017
@kgersen kgersen added this to In Progress in Alephs Jun 7, 2017
@kgersen kgersen changed the title timeGetTime used for Time class breaks operator after very long machine uptime timeGetTime breaks the Time class comparison operators after very long machine uptime Jun 7, 2017
@kgersen
Copy link
Owner Author

kgersen commented Aug 27, 2017

BT has a fix - once it's tested & validated, cherry pick the commit.

BackTrak added a commit to FreeAllegiance/Allegiance that referenced this issue Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Alephs
In Progress
Development

No branches or pull requests

1 participant