From b72e74810ce1f5815b0a01b661b3da6ee1b14ef2 Mon Sep 17 00:00:00 2001 From: Peter Collingbourne Date: Mon, 16 Mar 2020 18:14:13 -0700 Subject: Move crash_dump into the runtime APEX. A future change will introduce a version lock between linker and crash_dump. Move crash_dump into the runtime APEX alongside linker in order to ensure that they will be the same version even if the runtime APEX is updated. Bug: 135772972 Change-Id: Ic2eae31b6927eb0e8a62315ac141f50933c00bcc Merged-In: Ic2eae31b6927eb0e8a62315ac141f50933c00bcc --- debuggerd/handler/debuggerd_handler.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'debuggerd/handler/debuggerd_handler.cpp') diff --git a/debuggerd/handler/debuggerd_handler.cpp b/debuggerd/handler/debuggerd_handler.cpp index 8b4b6304f..9e3a649fa 100644 --- a/debuggerd/handler/debuggerd_handler.cpp +++ b/debuggerd/handler/debuggerd_handler.cpp @@ -83,7 +83,7 @@ using unique_fd = android::base::unique_fd_impl; #define CRASH_DUMP_NAME "crash_dump32" #endif -#define CRASH_DUMP_PATH "/system/bin/" CRASH_DUMP_NAME +#define CRASH_DUMP_PATH "/apex/com.android.runtime/bin/" CRASH_DUMP_NAME // Wrappers that directly invoke the respective syscalls, in case the cached values are invalid. #pragma GCC poison getpid gettid -- cgit v1.2.3