[test] Symbolize crash stacks in death tests on-demand Since death tests generate stack traces as a consequence of their expected crashes and stack traces are expensive to compute, stack traces in death test child processes are suppressed by default unless `--with-stack-traces` is on the command line. Along with this, emit a friendly message in place of symbolized stack traces in death tests child processes to tell developers how to see the stack traces if they wish. With this change, a death test that unexpectedly fails for which a stack trace has been suppressed will emit a message along the lines of: [ DEATH ] Received fatal exception EXCEPTION_ACCESS_VIOLATION [ DEATH ] Stack trace suppressed; retry with `--with-death-test-stack-traces --gtest_filter=ScopedHandleDeathTest.HandleVerifierTrackedHasBeenClosed`. Bug: 332745407 Change-Id: I800646417920b038098959ba1edd6514f8047dad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5423251 Reviewed-by: Peter Boström <pbos@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1284946}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.