Fix memory leak in ppc64 stackwalker

BUG=757166

Change-Id: I967a6903332b9c3d16b583f7fa4d3c9c44c2f729
Reviewed-on: https://chromium-review.googlesource.com/643267
Reviewed-by: Leonard Mosescu <mosescu@chromium.org>
Cr-Mirrored-From: https://chromium.googlesource.com/breakpad/breakpad
Cr-Mirrored-Commit: c4335f04356afe67cabc4cf5eb3d1f16294c3a03
diff --git a/processor/stackwalker_ppc64.cc b/processor/stackwalker_ppc64.cc
index 4fd9e74..fb2bac3 100644
--- a/processor/stackwalker_ppc64.cc
+++ b/processor/stackwalker_ppc64.cc
@@ -32,6 +32,7 @@
 // See stackwalker_ppc64.h for documentation.
 
 
+#include "common/scoped_ptr.h"
 #include "processor/stackwalker_ppc64.h"
 #include "google_breakpad/processor/call_stack.h"
 #include "google_breakpad/processor/memory_region.h"
@@ -112,7 +113,7 @@
     return NULL;
   }
 
-  StackFramePPC64* frame = new StackFramePPC64();
+  scoped_ptr<StackFramePPC64> frame(new StackFramePPC64());
 
   frame->context = last_frame->context;
   frame->context.srr0 = instruction;
@@ -138,7 +139,7 @@
   // return address value may access the context.srr0 field of StackFramePPC64.
   frame->instruction = frame->context.srr0 - 8;
 
-  return frame;
+  return frame.release();
 }