From 05d71ddb7e9e394d3b19a54a6149f50a4b52973d Mon Sep 17 00:00:00 2001
From: Valentin Schneider <valentin.schneider@arm.com>
Date: Tue, 10 Oct 2017 15:29:54 +0100
Subject: [PATCH] trace: Fix plotting when normalize_time=False

This fixes an oversight of 3dead2f2b36c589aae2d2f56a573bcac0bc3b8bc:
since we now use absolute windows with normalize_time=False, we
must use start_time along with the given window to determine the
x time range.
---
 libs/utils/trace.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libs/utils/trace.py b/libs/utils/trace.py
index 93a379e88..6d40e3251 100644
--- a/libs/utils/trace.py
+++ b/libs/utils/trace.py
@@ -314,7 +314,7 @@ class Trace(object):
         self._log.debug('Collected events spans a %.3f [s] time interval',
                        self.time_range)
 
-        self.setXTimeRange(self.window[0], self.window[1])
+        self.setXTimeRange(max(self.start_time, self.window[0]), self.window[1])
 
     def _scanTasks(self, df, name_key='comm', pid_key='pid'):
         """
-- 
GitLab