Don’t trigger EXC_CORPSE_NOTIFY on OS X 10.11

client/simulate_crash_mac_test.cc

 // Copyright 2014 The Crashpad Authors. All rights reserved.
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
 // You may obtain a copy of the License at
 //
 //     http://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
@@ skipping 210 matching lines @@
       // thread-level EXC_CRASH handler. To test that it will fall back to
       // trying the task-level EXC_CRASH handler, return a failure code, which
       // should cause SimulateCrash() to try the next target.
       EXPECT_EQ(kExceptionPortsTargetBoth, target_);
       return KERN_ABORTED;
     }
 
     ExcServerCopyState(
         behavior, old_state, old_state_count, new_state, new_state_count);
 
-    return ExcServerSuccessfulReturnValue(behavior, true);
+    return ExcServerSuccessfulReturnValue(exception, behavior, true);
   }
 
  private:
   // MachMultiprocess:
 
   void MachMultiprocessParent() override {
     if (target_ == kExceptionPortsTargetNone) {
       // The child does not have any EXC_CRASH handlers registered for its
       // thread or task targets, so no exception message is expected to be
       // generated. Don’t run the server at all.
@@ skipping 135 matching lines @@
           test_simulate_crash_mac.Run();
         }
       }
     }
   }
 }
 
 }  // namespace
 }  // namespace test
 }  // namespace crashpad