Print stack traces in child processes when browser tests failed.

content/common/sandbox_linux/sandbox_linux.cc

Index: content/common/sandbox_linux/sandbox_linux.cc
diff --git a/content/common/sandbox_linux/sandbox_linux.cc b/content/common/sandbox_linux/sandbox_linux.cc
index 952772ee648634f796e2aa4879461709a50ea69b..15472c39d91bc02383115612fe06ba02bb04c16c 100644
--- a/content/common/sandbox_linux/sandbox_linux.cc
+++ b/content/common/sandbox_linux/sandbox_linux.cc
@@ -140,13 +140,6 @@ void LinuxSandbox::PreinitializeSandbox() {
   sanitizer_args_.reset();
 #endif
 
-#if !defined(NDEBUG) || (defined(CFI_ENFORCEMENT) && !defined(OFFICIAL_BUILD))
-  // The in-process stack dumping needs to open /proc/self/maps and cache
-  // its contents before the sandbox is enabled.  It also pre-opens the
-  // object files that are already loaded in the process address space.
-  base::debug::EnableInProcessStackDumpingForSandbox();
-#endif  // !defined(NDEBUG)
-
   // Open proc_fd_. It would break the security of the setuid sandbox if it was
   // not closed.
   // If LinuxSandbox::PreinitializeSandbox() runs, InitializeSandbox() must run