commit 2dabfda8a25f2fd6747163dbb903e92f228dcf93
author Mateus Azis <azis@google.com> Mon Jul 01 10:56:18 2024 -0700
committer Mateus Azis <azis@google.com> Mon Jul 01 11:05:11 2024 -0700
tree 3ed776f8f6872122cafb64aa201c612e930cd3bb
parent 8cdf261e1752e331e746858dd80a602bc1cda698

Log process exit reason and subreason as strings.

These are currently logged as integers, but this makes them harder to
use during debugging. Log them as strings instead to make them more
helpful.

Test: flipped ActivityManagerDebugConfig and observed the following log
  when swiping up to kill an activity:

  07-01 10:54:48.698   784   813 I ActivityManager: note: ProcessRecord{d3e8a8 3858:com.android.dialer/u0a63} is being killed, reason: USER REQUESTED, sub-reason: REMOVE TASK, message: remove task

Change-Id: I84c0d8f54a01f9ee6d0e774a56d35b31b875ac14

services/core/java/com/android/server/am/ProcessList.java

diff --git a/services/core/java/com/android/server/am/ProcessList.java b/services/core/java/com/android/server/am/ProcessList.java
index 64e3e8e..97678aa 100644
--- a/services/core/java/com/android/server/am/ProcessList.java
+++ b/services/core/java/com/android/server/am/ProcessList.java
@@ -5491,8 +5491,9 @@
     void noteAppKill(final ProcessRecord app, final @Reason int reason,
             final @SubReason int subReason, final String msg) {
         if (DEBUG_PROCESSES) {
-            Slog.i(TAG, "note: " + app + " is being killed, reason: " + reason
-                    + ", sub-reason: " + subReason + ", message: " + msg);
+            Slog.i(TAG, "note: " + app + " is being killed, reason: "
+                    + ApplicationExitInfo.reasonCodeToString(reason) + ", sub-reason: "
+                    + ApplicationExitInfo.subreasonToString(subReason) + ", message: " + msg);
         }
         if (app.getPid() > 0 && !app.isolated && app.getDeathRecipient() != null) {
             // We are killing it, put it into the dying process list.