[coLinux-devel] [ colinux-Bugs-2551241 ] eclipse 3.4 won't start under devel-20090121

[SourceForge.net <no...@so...>]

Bugs item #2551241, was opened at 2009-01-31 04:47
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Arya (aryairani)
Assigned to: Nobody/Anonymous (nobody)
Summary: eclipse 3.4 won't start under devel-20090121

Initial Comment:
Running XP Pro SP2.

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-02-01 20:17

Message:
I'm afraid, this is not directly a problem of SSE-instructions. If that so,
then Eclipse would never run on CPU without XMM- and MMX-registers. The
disabling of SSE is to simple to be the condition for the crash. In the
last change, have disabled the CPU capability flags X86_FEATURE_MMX and
X86_FEATURE_XMM.

Similar does the kernel command line option "nofxsr" with X86_FEATURE_XMM
and X86_FEATURE_FXSR.
Please add "nofxsr" to coLinux config file and try the build
devel-20090120 with Eclipse.

I don't understand why Eclipse (or the Java behind) would use SSE
instructions. and why it should crash on MMX/XMM-disabled CPU. All
applications or kernel code, that use XMM/MMX-registers must save and
restore the registers and must do this within disabled interrupts. Inside
the kernel don't exist any code to global handle MMX/XMM-registers. All I
found was an exclusive usage of these registers in the source of raid for
i386.

In last lines of you log I found "CPU:total 1 (1 cores per cpu, 2 threads
per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2,
sse3, ht". So, from where Java got this informations about mmx and sse?
Does the Java runtime directly accessing these special registers? Arya,
please try "dpkg-reconfigure sun-java6-bin" under the non SSE coLinux.

I have JDK (Java 5) installed and a HelloWorld and a thread example runs
nice.
Arya, please try this on your system:
Download the example from:
 
http://www.idevelopment.info/data/Programming/java/threads/ThreadCountdownExtThread.java
than run:
  javac ThreadCountdownExtThread.java
  java ThreadCountdownExtThread

I have tested with packages sun-java5-bin and sun-java5-jdk installed.
You have Java 6, so please check there with sun-java6-bin and
sun-java6-jdk.

My cpuinfo under coLinux-20090121:
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
clflush dts acpi fxsr sse2 ss ht tm pbe nx constant_tsc pni monitor ds_cpl
est tm2 ssse3 xtpr lahf_lm

Eclipse is truly a very resource hungry application. Are you sure, that
you have enough memory?
Have you complete updated the kernel _and_ all modules for
devel-20090121?


----------------------------------------------------------------------

Comment By: Arya (aryairani)
Date: 2009-01-31 05:03

Message:
P.S. It's not a problem for me to go back to SSE-enabled builds, I don't
really need raid, I was just playing around with it earlier :)

----------------------------------------------------------------------

Comment By: Arya (aryairani)
Date: 2009-01-31 04:50

Message:
crap, I accidentally submitted an empty report when trying to upload crash
log.

no problem under 0.7.3 or devel-20090120, only under devel-20090121.

I think eclipse is executing some SSE instructions, thus crashing under
20090121...
I don't know under which circumstances javac emits SSE instructions, so I
wasn't able to construct a simpler test case...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2551241&group_id=98788