commit | 185ceda258c2fe6d2530182b174cec35d3ebfc1f | [log] [tgz] |
---|---|---|
author | Jesse McKenna <[email protected]> | Wed Mar 10 06:47:55 2021 |
committer | Chromium LUCI CQ <[email protected]> | Wed Mar 10 06:47:55 2021 |
tree | 470834058861677e3f46d66c561e7b6486389462 | |
parent | 23a1d68089e94410b185463e53a6ffd29aec4f34 [diff] |
Skip GetCommandLineString DCHECK in installer This change allows the installer to bypass a DCHECK in CommandLine. The DCHECK enforces that no arguments are parsed by QuoteForCommandLineToArgvW with syntax "%*", e.g., %1, %2, etc. These argument placeholders are called "insert sequences" and are used by the Windows shell. The DCHECK is intended to prevent new code from generating a command line for the Windows shell by parsing a string like "chrome.exe %1" instead of using the purpose-built GetCommandLineStringForShell(). However, setup.exe does generate a command line from string for itself that contains placeholders, and has no need for the special syntax created by GetCommandLineStringForShell(). Its use case is known to be safe because the insert sequence %1 is substituted by Google Update in a safe way. In order to support this call site, this change adds GetCommandLineStringWithUnsafeInsertSequences(), which skips the DCHECK, and invokes it in the setup code in question. Bug: 1181955 Change-Id: I4b7e64a7a83b887b32c57207ce4ac3850d40f874 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2727878 Reviewed-by: Greg Thompson <[email protected]> Reviewed-by: danakj <[email protected]> Commit-Queue: Jesse McKenna <[email protected]> Cr-Commit-Position: refs/heads/master@{#861452}
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.