This content has been marked as final. Show 3 replies
Different environment guarantees a different execution path.
And that is an excellent way to expose pointer bugs that previously did not impact the application.
If there is a return value how can this be a JVM crash? A crash is where an entire exits suddenly, possibly leaving a core dump or crash file of some kind behind it. This sounds like an error return from a JNI API call. In which case you should first consult the documentation for that API.
Or maybe you got the error from one call and proceeded regardless to call another API which crashed. In which case the answer is (a) don't ignore error codes, and (b) see above.
Yes, it is a JVM crash, I think don't explain it fine, I'm sorry.
The code call firstable to GetEnv and the return value is JNI_EDETACHED and
the next call is to AttachCurrentThread, it's in this call when the JVM crash.
I think that in all the return code, jni functions and third part api function, I'm checking the return value but I'll revise the code.
I'm going to separate the code to call only the minimal and necesary code to get the callback from the card PCI driver and test this.
I'll write the result here.
Edited by: 851285 on 12-abr-2011 1:09