I don't think the source is going to shed light on your issue but you can find it here [1]
The issue is that the 64-bit eclipe.exe is not able to load the 32-bit version of the library eclipse_1310.so and vise versa. Tom [1] http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/features/org.eclipse.equinox.executable.feature/library From: Ji Hoon Baik <uidlm1...@gmail.com> To: equinox-dev@eclipse.org Date: 07/16/2014 11:32 AM Subject: [equinox-dev] 32bit vs 64bit launcher Sent by: equinox-dev-boun...@eclipse.org Gents, Any help will be much appreciated on this matter. Our firm is in the process of migrating from 32-bit to 64-bit machines, and my team is refitting our RCP app to run on 64-bit machine. Initially our RCP app was failing to launch on 64-bit Win7, and we soon found out that using the x86_64 version of the equinox launcher solved the problem. However, we wanted to understand why we weren’t able to run our app while still using the x32 equinox launcher. We thought WOW64 should technically emulate 32-bit env and allow this library to run without problems. To find an answer, we also looked for source code for eclipse_1310.so jar (3.6’s shared dll), but to no avail. Would you be able to shed some light on this matter kindly? 1. What does this eclipse_1310.so do (and can we get the source code for it?) 2. What in it makes it necessary to keep 32-bit and 64-bit versions? Jason Baik I IT - CFT Sales From: Baik, Jason : Investment Bank (NYK) Sent: Wednesday, July 16, 2014 11:20 AM Subject: Theories for why SWS is not running with 32-bit launcher Reading further, I think it can be two things: 1. eclipse_1017.dll contains code that must run in kernel mode “Since WOW64 runs in user mode, all 32-bit application code must also run in user mode. This explains why 32-bit kernel mode device drivers and applications that rely on them, will not work under Windows 64-bit.” http://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm 2. Say eclipse_1017.dll runs entirely in user mode and can run on Win7 via WOW64. However, if the 32-bit and 64-bit eclipse_1017.dll’s have different search paths for JVMs, SWS might be failing to start due to the inability to find a JVM. “No -vm specified When no -vm is specified, the launcher looks for a virtual machine first in a jre directory in the root of eclipse and then on the search path. If java is found in either location, then the launcher looks for a jvm shared library (jvm.dll on Windows, libjvm.so on *nix platforms) relative to that java executable. If a jvm shared library is found the launcher loads it and uses the JNI invocation API to start the vm. If no jvm shared library is found, the launcher executes the java launcher to start the vm in a new process” http://help.eclipse.org/kepler/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/launcher.html If #2 is true, this probably proves why there’s no sign of JVM launching when our SWS fails on Win7. it might be worth experimenting: 1. Check Windows system logs to see if eclipse_1017.dll throws any errors 2. Provide an eclipse.ini file that specifies the 32 bit JVM location explicitly and try launching. _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
