#1420: Timers are never started ----------------------+----------------------------------------------------- Reporter: sbrandt | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: ET_2013_11 Component: Carpet | Version: ET_2013_05 Resolution: | Keywords: ----------------------+-----------------------------------------------------
Comment (by eschnett):
I think that timers that are running when a clock is created have clocks added that are not started. The problem is that Cactus does not keep track of whether a timer is running, and thus does not know whether to start such clocks. In other clocks, I either add a "bool is_running", or implicitly call start when the clock is created.