Make debugger and utility build on Win64

Make debugger and utility build on Win64 

Just c4267 build suppressions. 

BUG=166496
BUG=167187
TBR=thakis@chromium.org
R=thakis@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180216

[commit-bot: I haz the power, 2013-02-01 18:26:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jschuh@chromium.org/12095107/1

[Nico, 2013-02-01 18:27:27]

Isn't it better to fix these warnings instead?

[jschuh, 2013-02-01 18:32:41]

On 2013/02/01 18:27:27, Nico wrote:
> Isn't it better to fix these warnings instead?

Ideally yes, but it's not really feasible in the short term because our code is
polluted with an obscene number of blatant misuses of int. So, I'm using the
supressions 
to track what I need to fix, and then when I get bots up to catch regressions I
can go back and fix the tens of thousands of places where this is broken. (Can
you tell I'm frustrated by just what a mess this is?)

[Nico, 2013-02-01 18:41:55]

Justin explained to me in person that his team intends to clean these up with a
few people full-time within the next few months and this is to make sure no new
regressions creep in in the meantime, so lgtm.

(jschuh: You might want to look at clang's -fsanitize=integer, which is like
asan but for integer overflows etc. The test cases in
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20121126/157061.html
show some examples.)

[commit-bot: I haz the power, 2013-02-01 20:22:52]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jschuh@chromium.org/12095107/8003

[commit-bot: I haz the power, 2013-02-01 23:45:51]

Retried try job too often on win_rel for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...