[Ikvm-developers] IKVM and JNI
Brought to you by:
jfrijters
|
From: Дейзи Ч. <dai...@ma...> - 2009-09-23 08:36:51
|
Hi Jeroen, thanks for quick answer. Your suggestion regarding -Xcheck:jni looks very bright, because we DID use it for some time - the problem was that JRE5.0 worked fine with our dll, but JRE6.0 (updates 0-7) crached with hotspot log. But with -Xcheck:jni option it worked fine (Sun's bugs database said, that dlls compiled with Borland compiler don't save and restore on exit some FPU control word and recommended using this option). I didn't find now that exact bug, but these ones seem very similar: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6539718 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6487931 Fortunately, they admitted this as JVM fault, and since JRE 6.0 update 10 the problem disappeared! Hope this helps - maybe there is something like that in IKVM code? >Hi, >This is not exactly helpful. I can assure you that the native library is not loaded/unloaded for every call. >Have you tried running your code on Sun's Java with the -Xcheck:jni option? >Regards, >Jeroen |