Christophe,
Unfortunately this very insufficient info for debugging, but
technically you only need a single VirtualBoxManager - creating second
is a bug.
Having said this, you may post minimal testcase where you can reproduce
this issue, so we can look on the crash.
Nikolay.
22.04.2011 0:56, Christophe Devriese ?????:
I'm seeing jre crashes when trying to use the libvboxjxpcom api on 64
bits. Strangely, I seem to have this problem on both the openjdk and
sun VM's. Here's the backtrace :
V [libjvm.so+0x43ce80]
V [libjvm.so+0x44789a]
C [libvboxjxpcom.so+0xaf89]
C [libvboxjxpcom.so+0x15a1f]
Java_org_mozilla_xpcom_internal_XPCOMImpl_initXPCOMNative+0xc
j
org.mozilla.xpcom.internal.XPCOMImpl.initXPCOM(Ljava/io/File;Lorg/mozilla/xpcom/IAppFileLocProvider;)Lorg/mozilla/interfaces/nsIServiceManager;+3
j
org.mozilla.xpcom.Mozilla.initXPCOM(Ljava/io/File;Lorg/mozilla/xpcom/IAppFileLocProvider;)Lorg/mozilla/interfaces/nsIServiceManager;+6
j
org.virtualbox_4_0.VirtualBoxManager.createInstance(Ljava/lang/String;)Lorg/virtualbox_4_0/VirtualBoxManager;+50
Strangely, this doesn't happen on the first createInstance, only on
the second. How can I debug something like this ?
Christophe
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
