From f189215368da04e1e86dc349ef5b8ef82a14db09 Mon Sep 17 00:00:00 2001 From: Arnaud Legrand Date: Mon, 4 Feb 2013 14:04:14 +0100 Subject: [PATCH] Bug fix in trace management. When using periodicity, the first event indicates when events start and has undefined value (-1) as the value of the resource is used (e.g., the bandwidth value precised in the xml file). When looping with periodicity, the -1 value was used, which resulted in links with bandwidth -1.0 and could be noticed only in very specific situations. --- src/surf/trace_mgr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/surf/trace_mgr.c b/src/surf/trace_mgr.c index 5b45dab9bd..3d174c40a8 100644 --- a/src/surf/trace_mgr.c +++ b/src/surf/trace_mgr.c @@ -444,7 +444,7 @@ tmgr_trace_event_t tmgr_history_get_next_event_leq(tmgr_history_t h, trace_event->idx++; } else if (event->delta > 0) { /* Last element, checking for periodicity */ xbt_heap_push(h->heap, trace_event, event_date + event->delta); - trace_event->idx = 0; + trace_event->idx = 1; /* not 0 as the first event is a placeholder to handle when events really start */ } else { /* We don't need this trace_event anymore */ trace_event->free_me = 1; } -- 2.20.1