win: fix mismatched format macros

When building in Chromium:
../../third_party/crashpad/crashpad/util/process/process_memory_win.cc(95,74):  error: format specifies type 'unsigned long long' but the argument has type 'size_t' (aka 'unsigned int') [-Werror,-Wformat]
"range at 0x%llx, size 0x%llx completely inaccessible", address, size);
~~~~                                    ^~~~
%zx
../../third_party/crashpad/crashpad/util/process/process_memory_win.cc(103,72):  error: format specifies type 'unsigned long long' but the argument has type 'size_t' (aka 'unsigned int') [-Werror,-Wformat]
"start of range at 0x%llx, size 0x%llx inaccessible", address, size);

Change-Id: I820f0afee28d1220ca400780eac61de05bde10ef
Reviewed-on: https://chromium-review.googlesource.com/c/1323771
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Joshua Peraza <jperaza@chromium.org>
This commit is contained in:
Joshua Peraza 2018-11-07 10:18:29 -08:00 committed by Commit Bot
parent 71c75401c4
commit e287a3ab12

View File

@ -92,7 +92,9 @@ size_t ProcessMemoryWin::ReadAvailableMemory(VMAddress address,
// in the range.
if (ranges.empty()) {
LOG(ERROR) << base::StringPrintf(
"range at 0x%llx, size 0x%llx completely inaccessible", address, size);
"range at 0x%llx, size 0x%llx completely inaccessible",
address,
WinVMSize{size});
return 0;
}
@ -100,7 +102,9 @@ size_t ProcessMemoryWin::ReadAvailableMemory(VMAddress address,
// requested byte.
if (ranges.front().base() != address) {
LOG(ERROR) << base::StringPrintf(
"start of range at 0x%llx, size 0x%llx inaccessible", address, size);
"start of range at 0x%llx, size 0x%llx inaccessible",
address,
WinVMSize{size});
return 0;
}