From 010c36d22d74ffaed0ca397563fbc492fbef5f8b Mon Sep 17 00:00:00 2001 From: Stan Rokita Date: Tue, 21 Jan 2020 15:29:51 -0800 Subject: [PATCH] Fix the format specifier in assert log statements There are two ALOG_ASSERT calls in the HalProxyCallback::postEvents method that do not have the correct format specifier types. This causes a build error if you try to build with debug logs. Test: Build and load onto device Change-Id: I793b6fcd72dd13b07422af0e292a373a66b2c200 --- sensors/2.0/multihal/HalProxy.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sensors/2.0/multihal/HalProxy.cpp b/sensors/2.0/multihal/HalProxy.cpp index 03ff6051a8..37b7fcb427 100644 --- a/sensors/2.0/multihal/HalProxy.cpp +++ b/sensors/2.0/multihal/HalProxy.cpp @@ -652,12 +652,12 @@ void HalProxyCallback::postEvents(const std::vector& events, ScopedWakelo if (numWakeupEvents > 0) { ALOG_ASSERT(wakelock.isLocked(), "Wakeup events posted while wakelock unlocked for subhal" - " w/ index %zu.", + " w/ index %" PRId32 ".", mSubHalIndex); } else { ALOG_ASSERT(!wakelock.isLocked(), "No Wakeup events posted but wakelock locked for subhal" - " w/ index %zu.", + " w/ index %" PRId32 ".", mSubHalIndex); } mHalProxy->postEventsToMessageQueue(processedEvents, numWakeupEvents, std::move(wakelock));