Fixed bugs in GPU process startup on POSIX platforms. Added...

chrome/gpu/gpu_main.cc

Index: chrome/gpu/gpu_main.cc
===================================================================
--- chrome/gpu/gpu_main.cc	(revision 42147)
+++ chrome/gpu/gpu_main.cc	(working copy)
@@ -5,6 +5,7 @@
 #include "base/message_loop.h"
 #include "build/build_config.h"
 #include "chrome/common/chrome_constants.h"
+#include "chrome/common/chrome_switches.h"
 #include "chrome/common/main_function_params.h"
 #include "chrome/gpu/gpu_config.h"
 #include "chrome/gpu/gpu_process.h"
@@ -28,6 +29,11 @@
   InitCrashReporter();
 #endif
 
+  const CommandLine& command_line = parameters.command_line_;
+  if (command_line.HasSwitch(switches::kGpuStartupDialog)) {
+    ChildProcess::WaitForDebugger(L"Gpu");

[brettw, 2010/03/22 22:14:41]

This doesn't seem right. We have "startup dialog" which displays a message box
for you to manually attach to a renderer. But the analog for what you've done
here is the 
--wait-for-debugger-children described here:
http://www.chromium.org/developers/how-tos/debugging

It seems like it would be better to re-use that and add a new filter type than
create a new one.

+  }
+
   MessageLoop main_message_loop(MessageLoop::TYPE_UI);
   std::wstring app_name = chrome::kBrowserAppName;
   PlatformThread::SetName(WideToASCII(app_name + L"_GpuMain").c_str());