Break android_set_abort_message out of libc_logging.
libc_logging is getting statically linked into the crash handler
library, resulting in two copies of the abort message code existing in
processes, one in the linker, and one in the crash handler.
Move android_set_abort_message to its own file to solve this.
Bug: http://b/36862204
Test: /data/nativetest/debuggerd_test/debuggerd_test32
Change-Id: Ie198c5a3bb07645aa43296915c9a6752693f14a9
(cherry picked from commit 10ec9286ae843b0a84438699458ba17bff2f5602)
diff --git a/libc/Android.bp b/libc/Android.bp
index 5d0e8c7..8154470 100644
--- a/libc/Android.bp
+++ b/libc/Android.bp
@@ -775,6 +775,10 @@
"bionic/vdso.cpp",
"bionic/setjmp_cookie.cpp",
+ // The following must not be statically linked into libc_ndk.a, because
+ // debuggerd will look for the abort message in libc.so's copy.
+ "bionic/android_set_abort_message.cpp",
+
"bionic/__memcpy_chk.cpp",
"bionic/__strcat_chk.cpp",
"bionic/__strcpy_chk.cpp",