aboutsummaryrefslogtreecommitdiff
path: root/src/processor
diff options
context:
space:
mode:
authorprimiano@chromium.org <primiano@chromium.org>2015-04-13 17:45:17 +0000
committerprimiano@chromium.org <primiano@chromium.org>2015-04-13 17:45:17 +0000
commit353e4cd58528e7dea9d7d56b6b562be0aef1be81 (patch)
tree642afc22aee8cce497460d675a74e7e72fb01629 /src/processor
parentAdd address and reason for IN_PAGE_ERROR. (diff)
downloadbreakpad-353e4cd58528e7dea9d7d56b6b562be0aef1be81.tar.xz
Microdump processor: be more tolerant for different logcat formats
The current processor implementation is grepping for /google-breakpad( in the logcat lines, to filter out microdump lines, which by default look like this: W/google-breakpad( 3728): -----BEGIN BREAKPAD MICRODUMP----- Turns out that logcat format can vary, when passing optional arguments, and produce something like the following: 04-13 12:30:35.563 6531 6531 W google-breakpad: -----BEGIN ... In the latter case, the "/google-breakpad(" filter is too aggressive. This change is relaxing it, so it is compatible also with non-default logcat arguments. BUG=640 R=mmandlis@chromium.org Review URL: https://breakpad.appspot.com/2864002 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1442 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/processor')
-rw-r--r--src/processor/microdump.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/processor/microdump.cc b/src/processor/microdump.cc
index 91239855..bf628552 100644
--- a/src/processor/microdump.cc
+++ b/src/processor/microdump.cc
@@ -49,7 +49,7 @@
#include "processor/range_map-inl.h"
namespace {
-static const char kGoogleBreakpadKey[] = "/google-breakpad(";
+static const char kGoogleBreakpadKey[] = "google-breakpad";
static const char kMicrodumpBegin[] = "-----BEGIN BREAKPAD MICRODUMP-----";
static const char kMicrodumpEnd[] = "-----END BREAKPAD MICRODUMP-----";
static const char kOsKey[] = ": O ";