IPC fuzzer child process component

chrome/browser/chrome_content_browser_client.cc

Index: chrome/browser/chrome_content_browser_client.cc
diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc
index 5f8c5d275a3d232c066e26ed9d0f6af2344d1ed7..ad46fe01db7a12ba1a639984b48b5dc2227b158e 100644
--- a/chrome/browser/chrome_content_browser_client.cc
+++ b/chrome/browser/chrome_content_browser_client.cc
@@ -1334,6 +1334,14 @@ void ChromeContentBrowserClient::AppendExtraCommandLineSwitches(
   if (browser_command_line.HasSwitch(switches::kChromeFrame))
     command_line->AppendSwitch(switches::kChromeFrame);
 
+#if defined(ENABLE_IPC_FUZZER)
+  static const char* const kIpcFuzzerSwitches[] = {
+    switches::kIpcFuzzerTestcase,
+  };
+  command_line->CopySwitchesFrom(browser_command_line, kIpcFuzzerSwitches,
+                                 arraysize(kIpcFuzzerSwitches));

[jochen (gone - plz use gerrit), 2013/10/31 10:47:00]

for just one switch, using a static array seems to be overkill

[aedla, 2013/11/26 17:09:50]

I don't like it either. Other callers of CopySwitchesFrom() use this pattern
even for a single switch and I'd like to stay consistent. In an earlier patch
set I introduced CommandLine::CopySwitchFrom(), but I removed it after a debate
with brettw. I guess an argument for using an array is that adding new switches
is easy.

+#endif
+
   if (process_type == switches::kRendererProcess) {
     base::FilePath user_data_dir =
         browser_command_line.GetSwitchValuePath(switches::kUserDataDir);