From 6429e204940bc3de9051eac01a5e3d9f510a6109 Mon Sep 17 00:00:00 2001 From: dimitry Date: Tue, 12 Sep 2017 10:46:20 +0200 Subject: [PATCH] Recommend using pid instead of tid for gdbclient.py Using pid allows to examine other threads after gdb is attached to a crashing process. Test: make Change-Id: Ie4bab0925d7abde7f114791848fa5563db245c8e --- debuggerd/crash_dump.cpp | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/debuggerd/crash_dump.cpp b/debuggerd/crash_dump.cpp index dfc74fb9d..6ef3ed650 100644 --- a/debuggerd/crash_dump.cpp +++ b/debuggerd/crash_dump.cpp @@ -462,14 +462,14 @@ int main(int argc, char** argv) { if (wait_for_gdb) { // Use ALOGI to line up with output from engrave_tombstone. ALOGI( - "***********************************************************\n" - "* Process %d has been suspended while crashing.\n" - "* To attach gdbserver and start gdb, run this on the host:\n" - "*\n" - "* gdbclient.py -p %d\n" - "*\n" - "***********************************************************", - target, main_tid); + "***********************************************************\n" + "* Process %d has been suspended while crashing.\n" + "* To attach gdbserver and start gdb, run this on the host:\n" + "*\n" + "* gdbclient.py -p %d\n" + "*\n" + "***********************************************************", + target, target); } if (fatal_signal) {