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

clock_gettime() is not thread-safe #12

Merged
merged 1 commit into from Dec 27, 2015
Merged

clock_gettime() is not thread-safe #12

merged 1 commit into from Dec 27, 2015

Conversation

@vstinner
Copy link
Contributor

vstinner commented Oct 13, 2015

Don't use a global variable in clock_gettime(). Create a new timespec
object for each call to clock_gettime().

Don't use a global variable in clock_gettime(). Create a new timespec
object for each call to clock_gettime().
@felixonmars

This comment has been minimized.

Copy link

felixonmars commented Dec 8, 2015

A friendly ping :) I'd like to have this fix too...

@atdt

This comment has been minimized.

Copy link
Owner

atdt commented Dec 27, 2015

Yikes, sorry for the delay @felixonmars, @mdbooth, @Haypo.

atdt added a commit that referenced this pull request Dec 27, 2015
clock_gettime() is not thread-safe
@atdt atdt merged commit 1a85068 into atdt:master Dec 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.