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
This commit is contained in:
parent
2dac833ea8
commit
6429e20494
1 changed files with 8 additions and 8 deletions
|
@ -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) {
|
||||
|
|
Loading…
Reference in a new issue