Introduce bad_message.h for chrome and NaCl.

content/public/browser/browser_message_filter.cc

Index: content/public/browser/browser_message_filter.cc
diff --git a/content/public/browser/browser_message_filter.cc b/content/public/browser/browser_message_filter.cc
index cb75ff1b86a6e933cd0271deb01a7467eeb833a0..e99e0446f4ed07944f29d1af0c306b67bd9b6be2 100644
--- a/content/public/browser/browser_message_filter.cc
+++ b/content/public/browser/browser_message_filter.cc
@@ -176,11 +176,12 @@ bool BrowserMessageFilter::CheckCanDispatchOnUI(const IPC::Message& message,
   return true;
 }
 
-void BrowserMessageFilter::BadMessageReceived() {
+void BrowserMessageFilter::ShutdownForBadMessage() {
   base::CommandLine* command_line = base::CommandLine::ForCurrentProcess();
   if (command_line->HasSwitch(switches::kDisableKillAfterBadIPC))
     return;
 
+  // TODO(nick): Should this work differently on Android?

[Charlie Reis, 2015/05/22 20:55:52]

Maybe reference the fact that RenderProcessHostImpl::Shutdown special cases
Android?  

In the past, klobag@ pointed me to StopChildProcess in
child_process_launcher_android.cc, since the browser process can't kill
renderers directly there.  Not sure if that's available on the IO thread or not.

[ncarter (slow), 2015/05/26 22:59:04]

That's exactly what I was referring to with the TODO. I held off because I think
making that change will require adding a significant number of
PwnMessageReceived tests to make sure it works and I don't have a working linux
box to test the android changes handy at the moment.

I updated the comment to mention StopChildProcess explicitly.

   BrowserChildProcessHostImpl::HistogramBadMessageTerminated(
       PROCESS_TYPE_RENDERER);
   peer_process_.Terminate(content::RESULT_CODE_KILLED_BAD_MESSAGE, false);