tree db28baeec674f03e551cee29712178a981f584ee
parent 18af75ca6d175c1ae681a681098a6921cfcc52e4
author jam <jam@chromium.org> 1439782696 +0900
committer Qijiang Fan <fqj@google.com> 1591266488 +0900

Print stack traces in browser tests when any process crashes, or an assert fires.

The functionality to do this opens up security holes. Currently this was working only for debug Linux builds. However our trybots are release builds, and we need to be able to see stack traces from processes on all platforms and not just Linux (i.e. to be able to debug the large flakiness that occurred last week). This is disabled for official builds.

Also make release (non-official) builds print the callstack on asserts, just like debug builds. This makes it easier to debug test failures on the CQ (for example, DCHECKs for non-threadsafe usage of pointers).

Add a regression test that both renderer and browser process crashes print the callstack.

BUG=517488,358267,521148
NOPRESUBMIT=true

Committed: https://crrev.com/8ba532e170befc312e66d032587fa2ad04bac975
Cr-Commit-Position: refs/heads/master@{#343240}

Review URL: https://codereview.chromium.org/1291553003

Cr-Commit-Position: refs/heads/master@{#343626}


CrOS-Libchrome-Original-Commit: 79dc59ac7602413181079ecb463873e29a1d7d0a