Application error when calling CallStaticVoidMethod

Question

Dear all,
I'm calling a C-written program from java. The C-routine opens a usb dongle and gets data in a callback function. Each time when I call a CallStaticVoidMethod in order to return the data to my java counterpart, I get an Application Error which says: The instruction at "0x6d701845" referenced memory at "0x00000090". The memory could not be read. It looks like I'm calling the wrong method, but I can't get around this problem. I don't get a stacktrace and I don't get a java callback method called.
Any help is appreciated. See below for the code.
Regards,
Jeroen.
<c-code>
// Need global access to jclass and jmethod...
typedef struct
Bool connect;
int dongleId;
jclass WIN32_class;
jmethodID WIN32_method;
jmethodID WIN32_methodHw;
JNIEnv* WIN32_jenv;
int type;
} TState;
TState state;
JNIEXPORT jint JNICALL Java_com_philips_aurora_tools_nal_1interface_sniffer_StkUsbJni_connect
(JNIEnv * env, jobject obj, jint dongleId)
state.WIN32_jenv = env;
state.WIN32_class = (*env)->GetObjectClass(env, obj);
state.WIN32_method = (*env)->GetStaticMethodID(env, state.WIN32_class, "callback", "([B)V");
state.dongleId = dongleId;
errCode = (usbConnect)(dongleId,
(LPARAM) NULL /*??*/, // Don't use windows handles
(void*) receiveCallback,
(void*) handleNotifyCallback,
addr,
0x1 /*?*/);
static void receiveCallback(UCHAR dev, PUCHAR pMsg)
jbyteArray data = NULL;
int i, msgLength = 0;
data = (*state.WIN32_jenv)->NewByteArray(state.WIN32_jenv, msgLength);
(*state.WIN32_jenv)->SetByteArrayRegion(state.WIN32_jenv, data, 0, msgLength, (jbyte *)pMsg);
(*state.WIN32_jenv)->CallStaticVoidMethod(state.WIN32_jenv, state.WIN32_class, state.WIN32_method, data);
// BOOM!
(*state.WIN32_jenv)->ReleaseByteArrayElements(state.WIN32_jenv, data, (jbyte *)pMsg, 0);
(usbFree)(state.dongleId, pMsg);
</c-code>
<java-code>
public final class StkUsbJni implements StkUsbInterface {
     public native int connect(int dongleId);
     public native int disconnect();
     static void callback(byte[] aMessage) {
          StkCallBack.mwToolingMsg(aMessage);
</java-code>

Answer 1

Holding on to JNI info actually works very well like this.The fact that you have gotten it to work sometimes doesn't mean it is correct, it just means you were lucky.
stack is updated (corrupted) when I'm running in java.Which of course means that your C code is wrong.