Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

JNI: Unexpected behavior when executing codes after calling JNIEnv::ThrowNew #21

Closed
zhztheplayer opened this issue Jan 7, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@zhztheplayer
Copy link
Collaborator

JNIEnv::ThrowNew doesn't actually throw exceptions. The following of the codes will still be executed. Thus we should protect our JNI code from execution against any possible exceptions. Otherwise termination of whole process due to something like SIGSEGV
will be easily faced.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants