Handle EXC_RESOURCE and EXC_GUARD exceptions properly

client/crashpad_client_mac.cc

Index: client/crashpad_client_mac.cc
diff --git a/client/crashpad_client_mac.cc b/client/crashpad_client_mac.cc
index 2ac274d0f00cadeb2294e6e70baacff90df1dd24..e97e58b15f3dd11f8cfc07cc95f8b53008ece814 100644
--- a/client/crashpad_client_mac.cc
+++ b/client/crashpad_client_mac.cc
@@ -188,7 +188,8 @@ bool CrashpadClient::UseHandler() {
   // xnu-2422.115.4/bsd/uxkern/ux_exception.c catch_mach_exception_raise(). If a
   // core-generating signal (triggered through this hardware mechanism or a
   // software mechanism such as abort() sending SIGABRT) is unhandled and the
-  // process exits, the exception becomes EXC_CRASH. See 10.9.5
+  // process exits, or if the process is killed with SIGKILL for code-signing
+  // reasons, an EXC_CRASH exception will be sent. See 10.9.5
   // xnu-2422.115.4/bsd/kern/kern_exit.c proc_prepareexit().
   //
   // EXC_RESOURCE and EXC_GUARD do not become signals or EXC_CRASH exceptions.