From f2ed6b2161d58319f786a3a4fa4b3155f30c32e8 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Jos=C3=A9=20Fonseca?= <jfonseca@vmware.com>
Date: Thu, 1 Sep 2011 19:17:41 +0100
Subject: [PATCH] Always add calls for last frame.

When viewing traces of apps that crashed, the last frame is the most
interesting of all.

Furthermore, last frames actually do have markers, but no calls.
---
 gui/loaderthread.cpp | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/gui/loaderthread.cpp b/gui/loaderthread.cpp
index 03f0ccd..10a787b 100644
--- a/gui/loaderthread.cpp
+++ b/gui/loaderthread.cpp
@@ -91,14 +91,9 @@ void LoaderThread::run()
             call = p.parse_call();
         }
     }
-    //last frames won't have markers
-    //  it's just a bunch of Delete calls for every object
-    //  after the last SwapBuffers
     if (currentFrame) {
-        if (!frames.count()) {
-            calls.squeeze();
-            currentFrame->setCalls(calls, binaryDataSize);
-        }
+        calls.squeeze();
+        currentFrame->setCalls(calls, binaryDataSize);
         frames.append(currentFrame);
         currentFrame = 0;
     }
-- 
2.43.0