win: Don't omit frame pointers

win: Don't omit frame pointers

Chrome already always does this. Without this, RtlCaptureContext() gets
confused in some test cases.

Also, add /Zo https://msdn.microsoft.com/en-us/library/dn785163.aspx
which is helpful when debugging opt builds.

R=mark@chromium.org
BUG=crashpad:50
Committed: https://chromium.googlesource.com/chromium/mini_chromium/+/302e4e7d9aa0a8d39ad62b193a4c8a8357ad9d0c

[scottmg, 2015-09-16 21:27:33]

Oops, after saying in that other thread that *chrome* always does this, it took
me a while to connect that crashpad has its own build/common.gypi.

[Mark Mentovai, 2015-09-16 21:30:23]

LGTM, although I think that once we replace RtlCaptureContext() (bug
crashpad:53), we can let FPO be on again.

[scottmg, 2015-09-16 21:32:25]

On 2015/09/16 21:30:23, Mark Mentovai - August is over wrote:
> LGTM, although I think that once we replace RtlCaptureContext() (bug
> crashpad:53), we can let FPO be on again.

Yeah, we should at least make sure it works correctly.

It's been disabled in Microsoft apps for years, and we couldn't measure any perf
delta on Chrome fwiw, so I'm not sure it matters too much either way.

[scottmg, 2015-09-16 21:32:47]

Committed patchset #1 (id:1) manually as
302e4e7d9aa0a8d39ad62b193a4c8a8357ad9d0c (presubmit successful).