GitLab

Crash can locate particular entries in a stack by scanning for start &
end markers with unusual values.  We add start & end markers around the
|str_stack| copy of the LogMessage string, created when we're about to
crash the process due to a FATAL level log message.

This was originally landed with review:
https://chromium-review.googlesource.com/c/1201344
which was reverted because MSan bots (correctly) failed due to the test's
scanning of uninitialized stack memory. Since the test can't avoid doing
that, we simply disable it under both ASan and MSan.

Bug: 802393
Change-Id: Icd87f258aeb9556ab8e68d3e3431e80c01f1d3f0
Reviewed-on: https://chromium-review.googlesource.com/c/1292597Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Commit-Queue: Albert J. Wong <ajwong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601399}