Run mig to generate the exc and mach_exc interfaces

Run mig to generate the exc and mach_exc interfaces.

mach_exc is necessary because libSystem doesn’t contain this at all. exc
is necessary too, however: the copy in libSystem relies on the server
callbacks being externally defined symbols, which is cheesey.
Additionally, some Crashpad code wants to call internal validation
(“check”) routines that are not normally accessible to outside callers
via the copy of exc in libSystem, but they are made accessible here by
processing mig’s output in this Python script.

R=rsesek@chromium.org

Committed: https://chromium.googlesource.com/crashpad/crashpad/+/5a0b7827ff367c07828e2e23e4be9f05bfe2af68

[Mark Mentovai, 2014-09-04 22:56:29]

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

[Mark Mentovai, 2014-09-04 22:56:30]

How about a little Python for a change?

[Robert Sesek, 2014-09-05 16:32:38]

https://codereview.chromium.org/541213002/diff/1/util/mach/mig.py
File util/mach/mig.py (right):

https://codereview.chromium.org/541213002/diff/1/util/mach/mig.py#newcode22
util/mach/mig.py:22: # This function rewrites the file at |implementation| by
adding
Shouldn't these be docstrings?

https://codereview.chromium.org/541213002/diff/1/util/mach/mig.py#newcode75
util/mach/mig.py:75: # compilation unit |declarations| can be a list of
additional declarations to
unit.

[Mark Mentovai, 2014-09-05 16:48:54]

Updated.

[Robert Sesek, 2014-09-05 17:16:40]

LGTM

[Mark Mentovai, 2014-09-05 17:27:10]

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