Stop explicitly setting strip_absolute_paths_from_debug_symbols to true.

It's been defaulted to true for a while now on Linux and Windows,
so rely on the default setting instead.

Bug: none
Change-Id: Id24297dff08b28ee5e28f6cb6267018a4a1443e1
Reviewed-on: https://chromium-review.googlesource.com/c/1294298Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601777}

docs/disassemble_code.md

@@ -41,7 +41,6 @@ is_official_build = true
 dcheck_always_on = true
 is_component_build = false
 is_debug = false
-strip_absolute_paths_from_debug_symbols = true
 blink_symbol_level = 1
 symbol_level = 1
 

docs/linux_debugging.md

@@ -275,11 +275,10 @@ your "gn args".
 
 ### Source level debug with -fdebug-compilation-dir
 
-When you enable GN config `strip_absolute_paths_from_debug_symbols`, this is
-enabled by default for goma on Linux build, you need to add following command
-to your `~/.gdbinit` for source level debugging to load customized
-[gdbinit](../tools/gdb/gdbinit) or copy the content of the file to your
-`~/.gdbinit`.
+When `strip_absolute_paths_from_debug_symbols` is enabled (which is the
+default) you need to add following command to your `~/.gdbinit` for source
+level debugging to load customized [gdbinit](../tools/gdb/gdbinit) or copy the
+content of the file to your `~/.gdbinit`.
 
 ```
 source path/to/chromium/src/tools/gdb/gdbinit

tools/mb/mb_config.pyl

@@ -1930,12 +1930,7 @@
     },
 
     'goma': {
-      # The MB code will properly escape goma_dir if necessary in the GYP
-      # code path; the GN code path needs no escaping.
-      # We also set strip_absolute_paths to ensure that we can get deterministic
-      # builds. This isn't just on by default when goma is on so that devs
-      # can do goma builds but still be able to debug by default.
-      'gn_args': 'use_goma=true strip_absolute_paths_from_debug_symbols=true',
+      'gn_args': 'use_goma=true',
     },
 
     'gpu_fyi_tests': {