- Under a normal situation, if an exception happens in managed, the stack trace will be printed to logcat. - Hitherto, the Binder#execTransact call silently caught exceptions and passed them to the remote side with Parcel#writeException - Although this behavior might be acceptable when there is a remote side, for FLAG_ONEWAY calls the exception effectively disappeared. - From the user point of view, it looked like code execution "halted" when an exception was thrown. This tries to make the binder exception handling behavior more like normal, by printing the exception to the log, to give a better indication of what happened. Change-Id: I1f37f0468f61e766a71db60d2fda2104936ab096
…
…
Description
No description provided
Languages
Java
77.3%
Kotlin
9.2%
PowerBuilder
6.6%
C++
5.5%
AIDL
1%