| commit | fdeb93249629bb8510eb528dc97ffbd4fa1eeebc | [log] [tgz] |
|---|---|---|
| author | Arthur Milchior <arthurmilchior@google.com> | Wed May 11 14:55:11 2022 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 11 14:55:11 2022 |
| tree | 8fcbab04d837f7abbf0424d57d7a445d6926ff7c | |
| parent | d14d6cc602c51d1e1e74e0587454360be7467280 [diff] |
[base] Add a new line between dcheck message and stack string The first two lines are currently 6096:259:FATAL:observer_list.h(263)] Check failed: observers_.empty(). 0 ios_chrome_unittests 0x000000010a178fff base::debug::CollectStackTrace(void**, unsigned long) + 31 1 ios_chrome_unittests 0x0000000109f2371a base::debug::StackTrace::StackTrace(unsigned long) + 58 And now it becomes 6096:259:FATAL:observer_list.h(263)] Check failed: observers_.empty(). 0 ios_chrome_unittests 0x000000010a178fff base::debug::CollectStackTrace(void**, unsigned long) + 31 1 ios_chrome_unittests 0x0000000109f2371a base::debug::StackTrace::StackTrace(unsigned long) + 58 In particular, it repairs alignment Bug: None Change-Id: I70e3d12afbbbae8f0784b16a8bb9d0016e167c58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3634685 Auto-Submit: Arthur Milchior <arthurmilchior@google.com> Commit-Queue: Arthur Milchior <arthurmilchior@google.com> Reviewed-by: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/main@{#1002086}
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.