3party/crashpad
0
0
Fork 0
mirror of https://github.com/chromium/crashpad.git synced 2024-12-27 15:32:10 +08:00
Code Issues Projects Releases Wiki Activity

win: Add some explanation of .com/.exe for crashpad_handler

Browse Source 
R=mark@chromium.org
BUG=

Change-Id: Iedc42c7a157967c6fc316c04bb0bbb1f97dadf8d
Reviewed-on: https://chromium-review.googlesource.com/371963
Reviewed-by: Mark Mentovai <mark@chromium.org>
This commit is contained in:
Scott Graham 2016-08-24 16:00:10 -07:00
parent 866e60749c
commit 357c7c7b7b
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
handler/crashpad_handler.ad
View File

@ -60,6 +60,16 @@ well as the client’s process handle for the client to exit cleanly without
crashing. When a server started via the *--handshake-handle* mechanism loses all
of its clients, it exits after allowing any upload in progress to complete.
On Windows, this executable is built by default as a Windows GUI app, so no
console will appear in normal usage. This is the version that will typically be
used. A second copy is also made with a +.com+ extension, rather than +.exe+. In
this second copy, the PE header is modified to indicate that it's a console app.
This is useful because the +.com+ is found in the path before the +.exe+, so
when run normally from a shell using only the basename (without an explicit
+.com+ or +.exe+ extension), the +.com+ console version will be chosen, and so
stdio will be hooked up as expected to the parent console so that logging output
will be visible.
It is not normally appropriate to invoke this program directly. Usually, it will
be invoked by a Crashpad client using the Crashpad client library, or started by
another system service. On OS X, arbitrary programs may be run with a Crashpad