#242 Timer issue in VirtualizeTimerC$fireTimers

[Ian Elbury]

Problem:

If a timer is started from another timers fired
event, there is the possibility of the timer firing
immediatly. If the timer is started from a task, then
everything works correctly.

This problem is caused by the fact that the
variable 'now' is passed into fireTimers and is stale
if any timers take longer then one tick of the clock
to process. This problem is especially evident on
some platforms when running with a debugger (I am
running a LPC2138 arm processor).

Solution:

I solved the problem by calculating 'now' before
evaluating the requirement to signal a timer.

Change:

"uint32_t elapsed = call now - timer->t0;"

to

"uint32_t elapsed = call TimerFrom.getNow() - timer-
>t0;"

[David Gay]

Logged In: YES
user_id=398311
Originator: NO

This needs fixing.