Fix stack trace symbolization on Windows.

Fix stack trace symbolization on Windows.

(Joint work with @DavidYen)

This CL requires a companion Chromium CL in order to fix stack trace
symbolization on Windows. It makes the following changes:

 - The Windows toolchain installed on the bots and for Chromium
   developers is now versioned by hash. It's impractical to parse the
   hashes, since doing so would add another strong tie between the
   Catapult and Chromium workspaces, so instead support wildcards in
   Telemetry's path utilities for finding cdb.exe. (Any version of
   this tool will work.)

 - It deletes code associated with the obsolete crash_service.
   Chromium on Windows now uses Crashpad.

 - It relies on Crashpad to honor the BREAKPAD_DUMP_LOCATION
   environment variable. (This requires a Chromium change.)

Once this CL is rolled into Chromium, tools/perf's stack trace
unittest will be enabled on Windows, preventing this functionality
from regressing again.

BUG=chromium:561763
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/253a6f9b5e6eef06b8e8a80f8c122e8cf9ed9b8d

[Ken Russell (switch to Gerrit), 2016-04-04 19:02:12]

kbr@chromium.org changed reviewers:
+ nednguyen@google.com

[Ken Russell (switch to Gerrit), 2016-04-04 19:02:13]

Ned: please review. Thanks.

David, Scott: FYI. Will upload the dependent Chromium CL for your review
shortly.

Note: I had to upload this with --bypass-hooks because Telemetry's presubmit
check complained about binary_dependencies.json; from my Windows workstation, it
wanted to add a ^M after every line, which seemed wrong.

[nednguyen, 2016-04-04 19:11:54]

On 2016/04/04 19:02:13, Ken Russell wrote:
> Ned: please review. Thanks.
> 
> David, Scott: FYI. Will upload the dependent Chromium CL for your review
> shortly.
> 
> Note: I had to upload this with --bypass-hooks because Telemetry's presubmit
> check complained about binary_dependencies.json; from my Windows workstation,
it
> wanted to add a ^M after every line, which seemed wrong.

lgtm

The code seems simpler, which is a great win!

[Ken Russell (switch to Gerrit), 2016-04-04 20:24:09]

The CQ bit was checked by kbr@chromium.org

[commit-bot: I haz the power, 2016-04-04 20:24:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1860643002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1860643002/1

[commit-bot: I haz the power, 2016-04-04 20:56:26]

Description was changed from

==========
Fix stack trace symbolization on Windows.

(Joint work with @DavidYen)

This CL requires a companion Chromium CL in order to fix stack trace
symbolization on Windows. It makes the following changes:

 - The Windows toolchain installed on the bots and for Chromium
   developers is now versioned by hash. It's impractical to parse the
   hashes, since doing so would add another strong tie between the
   Catapult and Chromium workspaces, so instead support wildcards in
   Telemetry's path utilities for finding cdb.exe. (Any version of
   this tool will work.)

 - It deletes code associated with the obsolete crash_service.
   Chromium on Windows now uses Crashpad.

 - It relies on Crashpad to honor the BREAKPAD_DUMP_LOCATION
   environment variable. (This requires a Chromium change.)

Once this CL is rolled into Chromium, tools/perf's stack trace
unittest will be enabled on Windows, preventing this functionality
from regressing again.

BUG=chromium:561763
==========

to

==========
Fix stack trace symbolization on Windows.

(Joint work with @DavidYen)

This CL requires a companion Chromium CL in order to fix stack trace
symbolization on Windows. It makes the following changes:

 - The Windows toolchain installed on the bots and for Chromium
   developers is now versioned by hash. It's impractical to parse the
   hashes, since doing so would add another strong tie between the
   Catapult and Chromium workspaces, so instead support wildcards in
   Telemetry's path utilities for finding cdb.exe. (Any version of
   this tool will work.)

 - It deletes code associated with the obsolete crash_service.
   Chromium on Windows now uses Crashpad.

 - It relies on Crashpad to honor the BREAKPAD_DUMP_LOCATION
   environment variable. (This requires a Chromium change.)

Once this CL is rolled into Chromium, tools/perf's stack trace
unittest will be enabled on Windows, preventing this functionality
from regressing again.

BUG=chromium:561763

Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-04-04 20:56:27]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

[scottmg, 2016-04-04 21:00:14]

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

[scottmg, 2016-04-04 21:00:15]

https://codereview.chromium.org/1860643002/diff/1/telemetry/telemetry/interna...
File telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py
(right):

https://codereview.chromium.org/1860643002/diff/1/telemetry/telemetry/interna...
telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py:191:
os.path.join('win_toolchain', 'vs2013_files', '*', 'win_sdk',
Does this work? I would expect vs_files/*/ after the switch to 2015.

[Ken Russell (switch to Gerrit), 2016-04-04 21:32:03]

On 2016/04/04 21:00:15, scottmg wrote:
>
https://codereview.chromium.org/1860643002/diff/1/telemetry/telemetry/interna...
> File telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py
> (right):
> 
>
https://codereview.chromium.org/1860643002/diff/1/telemetry/telemetry/interna...
> telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py:191:
> os.path.join('win_toolchain', 'vs2013_files', '*', 'win_sdk',
> Does this work? I would expect vs_files/*/ after the switch to 2015.

Argh. Thanks for catching this. There was a stale vs2013_files directory in my
depot_tools. I'll submit another CL.