content_browsertests: Ensure crash stack trace gets logged on Android

When a fatal signal is received in a content_browsertest, make sure the
stack trace is logged to both the (redirected) error log as well as the
system log (logcat) on Android. Previously the crash was only written to
logcat where we don't have any other log messages from the test for
context.

TBR=sky@chromium.org

Bug: 863341
Change-Id: I913f099a7f2ec976db986d3d648cbbcf51839847
Reviewed-on: https://chromium-review.googlesource.com/c/1456079
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630274}
1 file changed