<trclass="memdesc:ade0f63025116ed4ac3d89b598c9e7e49"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Starts a Crashpad handler process, performing any necessary handshake to configure it. <ahref="#ade0f63025116ed4ac3d89b598c9e7e49">More...</a><br/></td></tr>
<trclass="memdesc:a89f34445eca859e6c0d1876e8e171c25"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Sets the process’crash handler to a Mach service registered with the bootstrap server. <ahref="#a89f34445eca859e6c0d1876e8e171c25">More...</a><br/></td></tr>
<trclass="memdesc:a386bfb3704cadbfae7e684f5e569b5e6"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Sets the process’crash handler to a Mach port. <ahref="#a386bfb3704cadbfae7e684f5e569b5e6">More...</a><br/></td></tr>
<trclass="memdesc:a9f1d5d38e9b4f5781e3821551dcc39d5"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Sets the IPC pipe of a presumably-running Crashpad handler process which was started with <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a> or by other compatible means and does an IPC message exchange to register this process with the handler. However, just like <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a>, crashes are not serviced until <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> is called. <ahref="#a9f1d5d38e9b4f5781e3821551dcc39d5">More...</a><br/></td></tr>
<trclass="memdesc:af65cb31a1de191f1403c99c11e5cd855"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Retrieves the IPC pipe name used to register with the Crashpad handler. <ahref="#af65cb31a1de191f1403c99c11e5cd855">More...</a><br/></td></tr>
<trclass="memdesc:a58476a5f7a1910ad67ba2bce69ead38e"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Configures the process to direct its crashes to a Crashpad handler. <ahref="#a58476a5f7a1910ad67ba2bce69ead38e">More...</a><br/></td></tr>
<trclass="memdesc:a8ac211aa3a8cf278eb10f4058a7776fb"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Requests that the handler capture a dump even though there hasn't been a crash. <ahref="#a8ac211aa3a8cf278eb10f4058a7776fb">More...</a><br/></td></tr>
<trclass="memdesc:a87d1fa142b0bf7094fc66fef3135a64a"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Requests that the handler capture a dump using the given <em>exception_pointers</em> to get the <code>EXCEPTION_RECORD</code> and <code>CONTEXT</code>. <ahref="#a87d1fa142b0bf7094fc66fef3135a64a">More...</a><br/></td></tr>
<trclass="memdesc:a1a6a1e62d90a67db782664b1fe5a952f"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Configures the process to direct its crashes to the default handler for the operating system. <ahref="#a1a6a1e62d90a67db782664b1fe5a952f">More...</a><br/></td></tr>
<p>Requests that the handler capture a dump using the given <em>exception_pointers</em> to get the <code>EXCEPTION_RECORD</code> and <code>CONTEXT</code>. </p>
<p>This function is not necessary in general usage as an unhandled exception filter is installed by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a>.</p>
<dlclass="params"><dt>Parameters</dt><dd>
<tableclass="params">
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">exception_pointers</td><td>An <code>EXCEPTION_POINTERS</code>, as would generally passed to an unhandled exception filter. </td></tr>
<p>Requests that the handler capture a dump even though there hasn't been a crash. </p>
<dlclass="params"><dt>Parameters</dt><dd>
<tableclass="params">
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">context</td><td>A <code>CONTEXT</code>, generally captured by <aclass="el"href="namespacecrashpad.html#ac25486c6b4c38fc7c7868e978094edcf"title="Saves the CPU context. ">CaptureContext()</a> or similar. </td></tr>
<p>This method retrieves the IPC pipe name set by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a9f1d5d38e9b4f5781e3821551dcc39d5"title="Sets the IPC pipe of a presumably-running Crashpad handler process which was started with StartHandle...">SetHandlerIPCPipe()</a>, or a suitable IPC pipe name chosen by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a>. It is intended to be used to obtain the IPC pipe name so that it may be passed to other processes, so that they may register with an existing Crashpad handler by calling <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a9f1d5d38e9b4f5781e3821551dcc39d5"title="Sets the IPC pipe of a presumably-running Crashpad handler process which was started with StartHandle...">SetHandlerIPCPipe()</a>.</p>
<dlclass="section return"><dt>Returns</dt><dd>The full name of the crash handler IPC pipe, a string of the form <code>"\\.\pipe\NAME"</code>. </dd></dl>
<p>Sets the IPC pipe of a presumably-running Crashpad handler process which was started with <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a> or by other compatible means and does an IPC message exchange to register this process with the handler. However, just like <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a>, crashes are not serviced until <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> is called. </p>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">ipc_pipe</td><td>The full name of the crash handler IPC pipe. This is a string of the form <code>"\\.\pipe\NAME"</code>.</td></tr>
<p>Sets the process’crash handler to a Mach port. </p>
<p>This method does not actually direct any crashes to the Crashpad handler, because there are alternative ways to start or use an existing Crashpad handler. To begin directing crashes to the handler set by this method, call <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> after this method.</p>
<p>This method is only defined on OS X.</p>
<dlclass="params"><dt>Parameters</dt><dd>
<tableclass="params">
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">exception_port</td><td>An <code>exception_port_t</code> corresponding to a Crashpad exception handler service. </td></tr>
<p>Sets the process’crash handler to a Mach service registered with the bootstrap server. </p>
<p>This method does not actually direct any crashes to the Crashpad handler, because there are alternative ways to start or use an existing Crashpad handler. To begin directing crashes to the handler set by this method, call <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> after this method returns successfully.</p>
<p>This method is only defined on OS X.</p>
<dlclass="params"><dt>Parameters</dt><dd>
<tableclass="params">
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">service_name</td><td>The service name of a Crashpad exception handler service previously registered with the bootstrap server.</td></tr>
</table>
</dd>
</dl>
<dlclass="section return"><dt>Returns</dt><dd><code>true</code> on success, <code>false</code> on failure with a message logged. </dd></dl>
<p>This method does not actually direct any crashes to the Crashpad handler, because there are alternative ways to use an existing Crashpad handler. To begin directing crashes to the handler started by this method, call <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> after this method returns successfully.</p>
<p>On Mac OS X, this method starts a Crashpad handler and obtains a Mach send right corresponding to a receive right held by the handler process. The handler process runs an exception server on this port.</p>
<dlclass="params"><dt>Parameters</dt><dd>
<tableclass="params">
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">handler</td><td>The path to a Crashpad handler executable. </td></tr>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">database</td><td>The path to a Crashpad database. The handler will be started with this path as its <code>--database</code> argument. </td></tr>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">url</td><td>The URL of an upload server. The handler will be started with this URL as its <code>--url</code> argument. </td></tr>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">annotations</td><td>Process annotations to set in each crash report. The handler will be started with an <code>--annotation</code> argument for each element in this map. </td></tr>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">arguments</td><td>Additional arguments to pass to the Crashpad handler. Arguments passed in other parameters and arguments required to perform the handshake are the responsibility of this method, and must not be specified in this parameter. </td></tr>
<tr><tdclass="paramdir">[in]</td><tdclass="paramname">restartable</td><td>If <code>true</code>, the handler will be restarted if it dies, if this behavior is supported. This option is not available on all platforms, and does not function on all OS versions. If it is not supported, it will be ignored.</td></tr>
<p>The Crashpad handler must previously have been started by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a> or configured by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a89f34445eca859e6c0d1876e8e171c25"title="Sets the process’crash handler to a Mach service registered with the bootstrap server. ">SetHandlerMachService()</a>, <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a386bfb3704cadbfae7e684f5e569b5e6"title="Sets the process’crash handler to a Mach port. ">SetHandlerMachPort()</a>, or <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a9f1d5d38e9b4f5781e3821551dcc39d5"title="Sets the IPC pipe of a presumably-running Crashpad handler process which was started with StartHandle...">SetHandlerIPCPipe()</a>.</p>
<p>On Mac OS X, this method sets the task’s exception port for <code>EXC_CRASH</code>, <code>EXC_RESOURCE</code>, and <code>EXC_GUARD</code> exceptions to the Mach send right obtained by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a>. The handler will be installed with behavior <code>EXCEPTION_STATE_IDENTITY | MACH_EXCEPTION_CODES</code> and thread state flavor <code>MACHINE_THREAD_STATE</code>. Exception ports are inherited, so a Crashpad handler chosen by <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> will remain the handler for any child processes created after <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> is called. Child processes do not need to call <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a> or <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a> or be aware of Crashpad in any way. The Crashpad handler will receive crashes from child processes that have inherited it as their exception handler even after the process that called <aclass="el"href="classcrashpad_1_1CrashpadClient.html#ade0f63025116ed4ac3d89b598c9e7e49"title="Starts a Crashpad handler process, performing any necessary handshake to configure it...">StartHandler()</a> exits.</p>
<p>On Windows, this method sets the unhandled exception handler to a local function that when reached will "signal and wait" for the crash handler process to create the dump.</p>
<dlclass="section return"><dt>Returns</dt><dd><code>true</code> on success, <code>false</code> on failure with a message logged. </dd></dl>
<p>Configures the process to direct its crashes to the default handler for the operating system. </p>
<p>On OS X, this sets the task’s exception port as in <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a>, but the exception handler used is obtained from <aclass="el"href="namespacecrashpad.html#a47204f3a62646651e8f393cac2a6316b"title="Obtains the system’s default Mach exception handler for crash-type exceptions. ">SystemCrashReporterHandler()</a>. If the system’s crash reporter handler cannot be determined or set, the task’s exception ports for crash-type exceptions are cleared.</p>
<p>Use of this function is strongly discouraged.</p>
<dlclass="section warning"><dt>Warning</dt><dd>After a call to this function, Crashpad will no longer monitor the process for crashes until a subsequent call to <aclass="el"href="classcrashpad_1_1CrashpadClient.html#a58476a5f7a1910ad67ba2bce69ead38e"title="Configures the process to direct its crashes to a Crashpad handler. ">UseHandler()</a>.</dd></dl>
<dlclass="section note"><dt>Note</dt><dd>This is provided as a static function to allow it to be used in situations where a <aclass="el"href="classcrashpad_1_1CrashpadClient.html"title="The primary interface for an application to have Crashpad monitor it for crashes. ...">CrashpadClient</a> object is not otherwise available. This may be useful when a child process inherits its parent’s Crashpad handler, but wants to sever this tie. </dd></dl>
</div>
</div>
<hr/>The documentation for this class was generated from the following files:<ul>
<li>client/crashpad_client.h</li>
<li>client/crashpad_client_mac.cc</li>
<li>client/crashpad_client_win.cc</li>
</ul>
</div><!-- contents -->
<!-- start footer part -->
<hrclass="footer"/><addressclass="footer"><small>
Generated by  <ahref="http://www.doxygen.org/index.html">
