summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authoryuanhuihui <yuanhuihui@xiaomi.com>2017-03-18 19:34:31 +0800
committerAnton Hansson <hansson@google.com>2018-02-13 12:52:38 +0000
commite669ac2520df7a4c3313da8b53705a99b5369587 (patch)
tree09642856e34a924e9803d3bd218b01e720b14f02 /tools/aapt2/java/JavaClassGenerator.cpp
parenta869d143435d19153cb2c01d2c972b661e817bfa (diff)
fix misleading FATAL EXCEPTION IN SYSTEM PROCESS log
There will be the following situations about mApplicationObject: 1) fork app process will invoke ActivityThread.main(), then set mApplicationObject. 2) fork system_server, don't set mApplicationObject value. 3) using app_process fork process except zygote, will inovke RuntimeInit, don't set mApplicationObject value。 For example using command as below: app_process /system/bin com.android.commands.am.Am "$@", if this process throw uncaught exception,will output FATAL EXCEPTION IN SYSTEM PROCESS log, it's not in system process but in normal process。 so should add condition: Process.SYSTEM_UID == Process.myUid() BUG: 72759350 Test: manual Change-Id: Ie8d769e4149cd9b938577058de871c4f8db9efe5 Signed-off-by: yuanhuihui <yuanhuihui@xiaomi.com>
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions