Qt-jambi-interest Archive, October 2007
Qt Jambi demo crashes
Message 1 in thread
Hi all,
Trying to run Qt Jambi demo results in :
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb1296222, pid=6237, tid=3084503248
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_13-b05 mixed mode, sharing)
# Problematic frame:
# C [libQtGui.so.4.3.2+0x19c222] _Z17qt_memfill32_sse2Pjji+0x92
#
# An error report file with more information is saved
as /tmp/hs_err_pid6237.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
/usr/bin/qtjambi: line 10: 6237 Aborted
java -cp /usr/share/java/qtjambi.jar:. com.trolltech.launcher.Launcher
A Google search revealed I am not the only one hitting this, Any ideas?
Regards,
ismail
Message 2 in thread
Hi, Äsmail.
Äsmail DÃnmez wrote:
> Hi all,
>
> # C [libQtGui.so.4.3.2+0x19c222] _Z17qt_memfill32_sse2Pjji+0x92
>
If this is a version of Jambi that you have built from source, could you
try the Qt Jambi binary package to see if you can reproduce the problem
with it?
> #
> # An error report file with more information is saved
> as /tmp/hs_err_pid6237.log
>
We have seen reports of this bug before, but we are not able to
reproduce it, so any information about your OS, machine (e.g. is it a
dual core or single core processor), when exactly the application
crashes (what did you do to make it crash), etc. would be helpful. Also,
it would be very helpful to have above-mentioned log file, if you could
mail this to me privately.
Thank you.
-- Eskil
Message 3 in thread
Äsmail DÃnmez wrote:
> # C [libQtGui.so.4.3.2+0x19c222] _Z17qt_memfill32_sse2Pjji+0x92
> #
> # An error report file with more information is saved
> as /tmp/hs_err_pid6237.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> #
> /usr/bin/qtjambi: line 10: 6237 Aborted
> java -cp /usr/share/java/qtjambi.jar:. com.trolltech.launcher.Launcher
>
> A Google search revealed I am not the only one hitting this, Any ideas?
>
Looking into this further, it seems that it's an issue with SSE
instructions in Qt and the JVM from Java 1.5. We have not been able to
narrow it down further yet, but you should be able to avoid it in one of
the following three ways:
1. Run on a newer JVM (version 1.6)
2. Configure Qt without SSE instructions (-no-sse -no-sse2)
3. Run against a Qt Jambi binary package (which is built without SSE
instructions.)
I hope this helps you.
-- Eskil
Message 4 in thread
Eskil Abrahamsen Blomfeldt wrote:
> Looking into this further, it seems that it's an issue with SSE
> instructions in Qt and the JVM from Java 1.5. We have not been able to
> narrow it down further yet, but you should be able to avoid it in one of
> the following three ways:
>
> 1. Run on a newer JVM (version 1.6)
This indeed fixes the problem.
Thanks,
ismail
