Microdump processor: be more tolerant for different logcat formats

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

Committed: https://code.google.com/p/google-breakpad/source/detail?r=1442

[primiano]

Maria, can you PTAL to this very small change?

Note: this is not strictly needed for your server-side processor (so no need to
roll internally).
On the client side, we happened today to receive some logcat dumps in mail
attachments (so, not uploaded to feedback ag all) where the logcat format was
slightly different.

[mmandlis]

lgtm

[primiano]

Committed patchset #1 (id:1) manually as 1442 (presubmit successful).