[Jamvm-general] QT-Jambi sigsegv at startup issue.
Brought to you by:
rlougher
From: Xerxes R. <xe...@za...> - 2012-06-15 10:26:48
|
Hi I am testing JamVM git head + OpenJDK 6 1.11.1 against the qt-jambi framework on a 32bit x86 machine: http://qt-jambi.org/ - Qt Jambi 4.7 beta this is the current actively maintained community supported version. http://qt-project.org/wiki/Qt_Jambi - Qt Jambi 4.5.2_01. This is last version by the Qt team. Testcase: wget http://downloads.sourceforge.net/project/qtjambi/4.7.0-beta2/qtjambi-linux32-community-4.7.0-beta2.tar.gz tar zxvf qtjambi-linux32-community-4.7.0-beta2.tar.gz cd qtjambi-linux32-community-4.7.0-beta2 ./qtjambi.sh the ./qtjambi.sh launches: /usr/bin/java -jamvm -cp ./qtjambi-util-4.7.0.jar:./qtjambi-linux32-gcc-4.7.0.jar:./qtjambi-examples-4.7.0.jar:./qtjambi-designer-4.7.0.jar:./qtjambi-4.7.0.jar: com.trolltech.launcher.Launcher I get an immediate crash during qt-jambi startup while using jamvm in contrast both cacao and hotspot work to launch these qt-jambi examples. I hit the same issue for both the 4.7 and 4.5.2 version. Program received signal SIGSEGV, Segmentation fault. 0x003543d7 in executeJava () at interp.c:2182 2182 DEF_OPC_210(OPC_INVOKEVIRTUAL_QUICK, { (gdb) bt #0 0x003543d7 in executeJava () at interp.c:2182 #1 0x0033ba70 in executeMethodVaList (ob=0x0, class=0x993d3c50, mb=0x94334254, jargs=0xb7fdc300 "") at execute.c:129 #2 0x0033d3e6 in Jam_CallStaticVoidMethod (env=0x377900, clazz=0x993d3c50, methodID=0x94334254) at jni.c:1221 #3 0x0804baa9 in JavaMain () #4 0x00138d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #5 0x00242ace in clone () from /lib/i386-linux-gnu/libc.so.6 Cheers Xerxes |