Pass Mach message trailers to server handler functions

Pass Mach message trailers to server handler functions.

TEST=util_test ChildPortServer.*:ExcServerVariants.*:MachMessageUtil.*
R=rsesek@chromium.org

Committed: https://chromium.googlesource.com/crashpad/crashpad/+/0437bc53b660a43027dd938ac9752407bf705ebc

[Mark Mentovai, 2014-11-25 21:54:13]

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

[Mark Mentovai, 2014-11-25 21:54:14]

It bugged me that you’d lose the ability to receive a message trailer that was
specified for a mach_msg() receive if you use the MachMessageServer interface
(or the mach_msg_server() interface it’s based on), because the handler routines
don’t receive the pointer to the message header. Here, I’m breaking out the
trailer as a separate parameter where these handler routines are called, so that
the trailers remain accessible.

[Robert Sesek, 2014-12-01 20:51:39]

https://codereview.chromium.org/755313004/diff/20001/util/mach/exc_server_var...
File util/mach/exc_server_variants_test.cc (right):

https://codereview.chromium.org/755313004/diff/20001/util/mach/exc_server_var...
util/mach/exc_server_variants_test.cc:172: const mach_msg_trailer_t* Trailer()
const {
Why not use the function defined in mach_message_util.h?

[Mark Mentovai, 2014-12-01 20:59:32]

Good point. Updated.

[Robert Sesek, 2014-12-01 21:02:43]

LGTM

[Mark Mentovai, 2014-12-01 21:07:02]

Committed patchset #3 (id:40001) manually as
0437bc53b660a43027dd938ac9752407bf705ebc (presubmit successful).