From 59e632a292e961eb914a59fcbb4623143b355f51 Mon Sep 17 00:00:00 2001 From: Florian Mayer Date: Wed, 8 Mar 2023 14:06:22 -0800 Subject: [PATCH] Print number of frames liblog can drop data when debuggerd is overloaded, which leads to truncated tombstones. by adding the count separately, automation can easily see whether it is dealing with a truncated tombstone or not. Bug: 269537146 Change-Id: Ia991537efc0d6b57cbff23ee45af6521467aa20d --- debuggerd/libdebuggerd/tombstone_proto_to_text.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/debuggerd/libdebuggerd/tombstone_proto_to_text.cpp b/debuggerd/libdebuggerd/tombstone_proto_to_text.cpp index e4d68f86a..8e6abdfa1 100644 --- a/debuggerd/libdebuggerd/tombstone_proto_to_text.cpp +++ b/debuggerd/libdebuggerd/tombstone_proto_to_text.cpp @@ -190,6 +190,7 @@ static void print_backtrace(CallbackType callback, const Tombstone& tombstone, static void print_thread_backtrace(CallbackType callback, const Tombstone& tombstone, const Thread& thread, bool should_log) { CBS(""); + CB(should_log, "%d total frames", thread.current_backtrace().size()); CB(should_log, "backtrace:"); if (!thread.backtrace_note().empty()) { CB(should_log, " NOTE: %s",