Fix formatting specifier for MSVC++ 2013 compatibility.

Fix formatting specifier for MSVC++ 2013 compatibility.

The use of %zu in a printf format string is non-standard.  This change
is a follow-up to https://codereview.chromium.org/1417873007 to use the
standard PRIuS macro instead.

BUG=519022
TBR=brucedawson@chromium.org

Committed: https://crrev.com/1dbefc62bf1df69475bea39c5a41f7825c72a6b0
Cr-Commit-Position: refs/heads/master@{#357582}

[miu, 2015-11-03 05:14:05]

miu@chromium.org changed reviewers:
+ brucedawson@chromium.org

[miu, 2015-11-03 05:14:32]

Description was changed from

==========
Fix formatting specifier for MSVC++ 2013 compatibility.

The use of %zu in a printf format string is non-standard.  This change
is a follow-up to https://codereview.chromium.org/1417873007 to use the
standard PRIuS macro instead.

BUG=519022
==========

to

==========
Fix formatting specifier for MSVC++ 2013 compatibility.

The use of %zu in a printf format string is non-standard.  This change
is a follow-up to https://codereview.chromium.org/1417873007 to use the
standard PRIuS macro instead.

BUG=519022
TBR=brucedawson@chromium.org
==========

[miu, 2015-11-03 05:14:38]

The CQ bit was checked by miu@chromium.org

[commit-bot: I haz the power, 2015-11-03 05:14:49]

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

[commit-bot: I haz the power, 2015-11-03 07:32:25]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-03 07:32:26]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[miu, 2015-11-03 18:22:40]

The CQ bit was checked by miu@chromium.org

[commit-bot: I haz the power, 2015-11-03 18:25:09]

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

[commit-bot: I haz the power, 2015-11-03 19:51:59]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-03 19:52:41]

Patchset 1 (id:??) landed as
https://crrev.com/1dbefc62bf1df69475bea39c5a41f7825c72a6b0
Cr-Commit-Position: refs/heads/master@{#357582}

[tommycli, 2015-11-05 00:48:49]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1414883010/ by tommycli@chromium.org.

The reason for reverting is: Speculatively revert to try to fix this: 

http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20(Dr...

The error message is very obtuse, but seems to indicate it's some kind of string
formatting issue. Feel free to revert the revert if it doesn't fix the issue.

Tommy.

[tommycli, 2015-11-05 00:49:37]

On 2015/11/05 00:48:49, tommycli wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/1414883010/ by mailto:tommycli@chromium.org.
> 
> The reason for reverting is: Speculatively revert to try to fix this: 
> 
>
http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20(Dr...
> 
> The error message is very obtuse, but seems to indicate it's some kind of
string
> formatting issue. Feel free to revert the revert if it doesn't fix the issue.
> 
> Tommy.

First breaking build btw:
http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28...

[brucedawson, 2015-11-05 20:55:05]

It is unfortunate that the crash call stacks don't include symbols. Not having
that information makes this diagnosis extremely difficult when it should be
trivial.