[Docs] Update latest docs per wiki changes.

docs/linux_debugging.md

 # Tips for debugging on Linux
 
 This page is for Chromium-specific debugging tips; learning how to run gdb is
 out of scope.
 
 [TOC]
 
 ## Symbolized stack trace
 
 The sandbox can interfere with the internal symbolizer. Use `--no-sandbox` (but
@@ skipping 251 matching lines @@
 Use the `gdb-add-index` script (e.g.
 `build/gdb-add-index out/Debug/browser_tests`)
 
 Only makes sense if you run the binary multiple times or maybe if you use the
 component build since most `.so` files won't require reindexing on a rebuild.
 
 See
 https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-dev/gdb-add-index/chromium-dev/ELRuj1BDCL4/5Ki4LGx41CcJ
 for more info.
 
-Alternatively, specify:
-
-    linux_use_debug_fission=0
-
-in `GYP_DEFINES`. This improves load time of gdb significantly at the cost of
-link time.
+You can improve GDB load time significantly at the cost of link time by
+plitting symbols from the object files. In GN, set `use_debug_fission=false` in
+your "gn args". In GYP add `linux_use_debug_fission=0` to your `GYP_DEFINES`.
 
 ## Core files
 
 `ulimit -c unlimited` should cause all Chrome processes (run from that shell) to
 dump cores, with the possible exception of some sandboxed processes.
 
 Some sandboxed subprocesses might not dump cores unless you pass the
 `--allow-sandbox-debugging` flag.
 
 If the problem is a freeze rather than a crash, you may be able to trigger a
@@ skipping 254 matching lines @@
 [Running layout tests on Linux](layout_tests_linux.md) page.
 
 If you need to test something with hardware accelerated compositing
 (e.g., compiz), you can use `Xgl` (`sudo apt-get install xserver-xgl`). E.g.:
 
     Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer -screen 1024x768
 
 ## Mozilla Tips
 
 https://developer.mozilla.org/en/Debugging_Mozilla_on_Linux_FAQ