tmf: Fix unnecessary unknown state at beginning of call stack event list
authorPatrick Tasse <patrick.tasse@gmail.com>
Mon, 2 May 2016 19:53:23 +0000 (15:53 -0400)
committerPatrick Tasse <patrick.tasse@gmail.com>
Tue, 3 May 2016 15:24:20 +0000 (11:24 -0400)
It could be seen as a single pixel state at the beginning of the trace.

Change-Id: I48a601f37931ac3b7e2fcf056e988e9ae169d514
Signed-off-by: Patrick Tasse <patrick.tasse@gmail.com>
Reviewed-on: https://git.eclipse.org/r/71821
Reviewed-by: Hudson CI
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
tmf/org.eclipse.tracecompass.tmf.ui/src/org/eclipse/tracecompass/tmf/ui/views/callstack/CallStackView.java

index f15f9376f083a026a2a6b05d9696a12e4ded6d9c..885b3568f964ae6ac34f838d348a8f625f6acfec 100644 (file)
@@ -753,7 +753,7 @@ public class CallStackView extends AbstractTimeGraphView {
             List<ITmfStateInterval> stackIntervals = StateSystemUtils.queryHistoryRange(ss, entry.getQuark(), start, end - 1, resolution, monitor);
             eventList = new ArrayList<>(stackIntervals.size());
             long lastEndTime = -1;
-            boolean lastIsNull = true;
+            boolean lastIsNull = false;
             for (ITmfStateInterval statusInterval : stackIntervals) {
                 if (monitor.isCanceled()) {
                     return null;
This page took 0.026801 seconds and 5 git commands to generate.