Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 59e632a2 authored by Florian Mayer's avatar Florian Mayer
Browse files

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
parent 9089ec6b

debuggerd/libdebuggerd/tombstone_proto_to_text.cpp

+1 −0
Original line number Diff line number Diff line
@@ -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",