From 596fbb61bc8b0e1e20782b274addb9763385f239 Mon Sep 17 00:00:00 2001
From: Tobias Sargeant <tobiasjs@google.com>
Date: Wed, 7 Dec 2016 16:41:46 +0000
Subject: Log a message when microdump output is suppressed.

Change-Id: I11542ea9b702055e8f0b99c26cad2fea8681bce0
Reviewed-on: https://chromium-review.googlesource.com/417824
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
---
 src/client/linux/microdump_writer/microdump_writer.cc | 1 +
 1 file changed, 1 insertion(+)

(limited to 'src/client/linux/microdump_writer')

diff --git a/src/client/linux/microdump_writer/microdump_writer.cc b/src/client/linux/microdump_writer/microdump_writer.cc
index 2bcef8ab..6ed69ea9 100644
--- a/src/client/linux/microdump_writer/microdump_writer.cc
+++ b/src/client/linux/microdump_writer/microdump_writer.cc
@@ -166,6 +166,7 @@ class MicrodumpWriter {
   void Dump() {
     CaptureResult stack_capture_result = CaptureCrashingThreadStack(-1);
     if (stack_capture_result == CAPTURE_UNINTERESTING) {
+      LogLine("Microdump skipped (uninteresting)");
       return;
     }
 
-- 
cgit v1.2.1