aboutsummaryrefslogtreecommitdiff
path: root/src/common/linux/memory_mapped_file.cc
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/common/linux/memory_mapped_file.cc
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/common/linux/memory_mapped_file.cc')
0 files changed, 0 insertions, 0 deletions