Enable --wait-for-debugger for the browser process....

chrome/browser/browser_main.cc

Index: chrome/browser/browser_main.cc
===================================================================
--- chrome/browser/browser_main.cc	(revision 50518)
+++ chrome/browser/browser_main.cc	(working copy)
@@ -61,6 +61,7 @@
 #else
 #include "chrome/browser/translate/translate_manager2.h"
 #endif
+#include "chrome/common/child_process.h"
 #include "chrome/common/chrome_constants.h"
 #include "chrome/common/chrome_paths.h"
 #include "chrome/common/chrome_switches.h"
@@ -1373,6 +1374,14 @@
   bool record_search_engine = is_first_run && !profile->IsOffTheRecord();
 #endif
 
+    // ChildProcess:: is a misnomer unless you consider context.  Use
+    // of --wait-for-debugger only makes sense when Chrome itself is a
+    // child process (e.g. when launched by PyAuto).
+  if (parsed_command_line.HasSwitch(switches::kWaitForDebugger)) {
+    ChildProcess::WaitForDebugger(L"Browser");
+  }
+
+
   int result_code = ResultCodes::NORMAL_EXIT;
   if (parameters.ui_task) {
     // We are in test mode. Run one task and enter the main message loop.