Framework: Improve binder Error logging
In protracted cases, diagnostic code cannot retrieve any Java-side data. Add two specific cases and instanceof checks (which require no allocation etc), and a special message, so that aborts have meaningful data (in case logcat is missing). Sample: Abort message: 'JNI FatalError called: java.lang.Error thrown during binder transaction: (Unknown exception message) (Error was OutOfMemoryError) (toString() error was OutOfMemoryError)' Bug: 136482507 Test: m Test: manual Change-Id: I5c0c1d74ba8a6aeafee95b578a422a80b9899196
Loading
Please register or sign in to comment