Fix JNIEnv-on-wrong-thread abort message.
Update an incorrect abort message that claimed that thread A was using the JNIEnv from thread A (when the JNIEnv was in fact from another thread). Now, the message is e.g. JNI DETECTED ERROR IN APPLICATION: thread Thread[1,tid=628,Native,Thread*=0xb038b400,peer=0x75efc1f0,"main"] using JNIEnv* from thread Thread[6,tid=640,Runnable,Thread*=0xaa890800,peer=0x12c00ca0,"Binder:628_1"] Change-Id: I877a78c47e88d1e8a28bade8ea40be6bed58439f
Loading
Please sign in to comment