You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently the alarm handler tries to grab a lock to avoid clobbering
a change to the time-left counter on an interval change by another thread.
also, it currently continues even when it can't get the lock after 2 tries:
which perhaps should be re-thought, but that's orthogonal to the main point
of this issue, which is to come up with a lockless protocol for updating
the multiplexing timer state.
idea: count up and mod to avoid having to reset?
need to figure out how to handle intervals w/o a simple common factor
though.
From [email protected] on November 01, 2011 17:09:05
xref Dr. Memory issue #626
currently the alarm handler tries to grab a lock to avoid clobbering
a change to the time-left counter on an interval change by another thread.
also, it currently continues even when it can't get the lock after 2 tries:
which perhaps should be re-thought, but that's orthogonal to the main point
of this issue, which is to come up with a lockless protocol for updating
the multiplexing timer state.
idea: count up and mod to avoid having to reset?
need to figure out how to handle intervals w/o a simple common factor
though.
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=597
The text was updated successfully, but these errors were encountered: