Introduce bad_message.h for chrome and NaCl.

components/nacl/browser/nacl_host_message_filter.cc

Index: components/nacl/browser/nacl_host_message_filter.cc
diff --git a/components/nacl/browser/nacl_host_message_filter.cc b/components/nacl/browser/nacl_host_message_filter.cc
index 8ebfed40115abf896cf2b98e6b50ccfa1f22ff6c..5538f1e4e140021a5ea42c07fa442b45515ab582 100644
--- a/components/nacl/browser/nacl_host_message_filter.cc
+++ b/components/nacl/browser/nacl_host_message_filter.cc
@@ -5,6 +5,7 @@
 #include "components/nacl/browser/nacl_host_message_filter.h"
 
 #include "base/sys_info.h"
+#include "components/nacl/browser/bad_message.h"
 #include "components/nacl/browser/nacl_browser.h"
 #include "components/nacl/browser/nacl_file_host.h"
 #include "components/nacl/browser/nacl_process_host.h"
@@ -156,7 +157,9 @@ void NaClHostMessageFilter::LaunchNaClContinuation(
   content::RenderViewHost* rvh = content::RenderViewHost::FromID(
       render_process_id(), launch_params.render_view_id);
   if (!rvh) {
-    BadMessageReceived();  // Kill the renderer.
+    bad_message::ReceivedBadMessage(
+        this, bad_message::NACL_LAUNCH_CONTINUATION_BAD_ROUTING_ID);

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

Your name looks nicer, but the convention would be to start with a class name
abbreviation (NHMF_).  Should we be consistent with the others here?  (I'm
probably ok leaving it.)

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

Changed to NHMF_ and NFH_. I used NACL_ originally because the first usage I hit
(in nacl_file_host.cc) was outside of any class.

+    delete reply_msg;
     return;
   }
 
@@ -358,7 +361,8 @@ void NaClHostMessageFilter::OnGetNexeFd(
   if (!cache_info.pexe_url.is_valid()) {
     LOG(ERROR) << "Bad URL received from GetNexeFd: " <<
         cache_info.pexe_url.possibly_invalid_spec();
-    BadMessageReceived();
+    bad_message::ReceivedBadMessage(this,
+                                    bad_message::NACL_GET_NEXE_FD_BAD_URL);
     return;
   }