tree e17a7053567d0246e2619bc8d35ef3f3d61cfd6f
parent b7709140a9818dbe7bc2f3609479043d3e1e968d
author Vignesh Venkatasubramanian <vigneshv@google.com> 1684797572 -0700
committer Wan-Teh Chang <wtc@google.com> 1684862513 -0700

android_jni: Handle JNI exceptions

When calling JNI functions, the default behavior is that the native
code execution will continue and a pending exception will be queued
to be thrown when the control goes back to the Java layer.

This is not desirable when multiple JNI calls are being made and the
second one depends on the successful execution of the first. Suppress
JNI level exceptions and simply return an error from those functions
instead of throwing a JNI exception in the java layer. This also
avoids some SIGABRTs in the native code.

Also, add nullptr checks for return values of FindClass and
GetFieldID.