In NDK you have to attach the current (native) thread to JVM, before yout can get a valid JNIEnv* for later use.
This machanism works quite well with the NDK compiler but it crashed while using Snapdragon compiler.
In NDK documentation it is written that only POSIX threads can be attached to JVM. Would it be the reason that Snapdragon compiler could be using another thread implementation?
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
The Snapdragon LLVM compiler does not use a different thread implmentation. It relies on NDK libraries for thread functionality.
Can you post a cut-down test case that will help us analyze the problem?
Thanks