win: Add CrashpadClient::GetHandlerIPCPipe()

win: Add CrashpadClient::GetHandlerIPCPipe()

For multiprocess architectures, this method allows the pipe used for
registration to be obtained from CrashpadHandler, even when
CrashpadHandler chooses its own name. This may happen if the handler is
not running on a well-known pipe name but was instead started by
CrashpadHandler::StartHandler(). If Chrome uses this interface, for
example, the browser process will need to call
CrashpadClient::GetHandlerIPCPipe() and pass the pipe name to its child
processes.

R=scottmg@chromium.org

Committed: https://chromium.googlesource.com/crashpad/crashpad/+/a30db914afae7904237b9ccd9576828808868f34

[Mark Mentovai, 2015-11-02 22:11:44]

mark@chromium.org changed reviewers:
+ scottmg@chromium.org

[scottmg, 2015-11-02 22:15:40]

lgtm

https://codereview.chromium.org/1427163004/diff/1/client/crashpad_client.h
File client/crashpad_client.h (right):

https://codereview.chromium.org/1427163004/diff/1/client/crashpad_client.h#ne...
client/crashpad_client.h:81: //! The IPC pipe name (somehow) encodes enough
information so that
This paragraph doesn't make sense any longer.

[Mark Mentovai, 2015-11-03 00:08:46]

https://codereview.chromium.org/1427163004/diff/1/client/crashpad_client.h
File client/crashpad_client.h (right):

https://codereview.chromium.org/1427163004/diff/1/client/crashpad_client.h#ne...
client/crashpad_client.h:81: //! The IPC pipe name (somehow) encodes enough
information so that
scottmg wrote:
> This paragraph doesn't make sense any longer.

Removed.

[Mark Mentovai, 2015-11-03 04:15:26]

Committed patchset #2 (id:20001) manually as
a30db914afae7904237b9ccd9576828808868f34 (presubmit successful).