From 96d6745fe4dd110d2f23e3811e36c798a75dd2a7 Mon Sep 17 00:00:00 2001 From: Gavin Corkery Date: Tue, 10 Dec 2019 23:00:24 +0000 Subject: [PATCH] Store crashing process name in sysprop As part of Watchdog-triggered rollback logging, it would be useful to know the service which has caused updatable_crashing to be set. Store this in a new property ro.init.updatable_crashing_process_name. Test: manual Bug: 146415463 Change-Id: Iffa38b2b746abbb5d823a8d69b7b8d2456836f4e Merged-In: Iffa38b2b746abbb5d823a8d69b7b8d2456836f4e (cherry picked from commit 5d0deb563d252ab41ea9fc0107477a6b738afbb9) --- init/service.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/init/service.cpp b/init/service.cpp index ccc37b70c..2db548efe 100644 --- a/init/service.cpp +++ b/init/service.cpp @@ -387,6 +387,7 @@ void Service::Reap(const siginfo_t& siginfo) { LOG(ERROR) << "updatable process '" << name_ << "' exited 4 times " << (boot_completed ? "in 4 minutes" : "before boot completed"); // Notifies update_verifier and apexd + property_set("ro.init.updatable_crashing_process_name", name_); property_set("ro.init.updatable_crashing", "1"); } }