Re: [equinox-dev] 32bit vs 64bit launcher
Thanks alot for all the pointers. Really appreciated. It turns out I was distracted too much by the dll in the launcher plugin. I was so hung up on the idea that the native code in eclipse_*.dll must be causing all the trouble. Looking at the source Tom pointed me to, I now see that the dll has no bearing on the rcp crashing or not, but it's only for displaying the splash before SWT is loaded by the framework... The actual problem I failed to spot was: 1. I was running the app unknowingly with 32-bit JVM 2. I replaced 32-bit SWT thinking it won't be needed. 3. I wasn't aware Eclipse-PlatformFilter was filtering out 64-bit SWT Thanks again all.. > Date: Wed, 16 Jul 2014 21:22:16 +0100 > From: Alex Blewitt > To: Equinox development mailing list > Subject: Re: [equinox-dev] 32bit vs 64bit launcher > Message-ID: <2e717927-0c34-4d4d-b23d-a3b42811a...@gmail.com> > Content-Type: text/plain; charset="utf-8" > > You might find that a wow64 launch of Eclipse 32 should work, but to do so > needs to know its in 32 bit mode. I believe that the auto detection will > still think it's in 64 bit mode even with 32 bit wow and so the 32 bit > launcher looks for the 64 bit library and then fails to load or not find it. > > You may find running with -Dosgi.arch=x86 will allow you to launch as > 32bit depending on which part of the process is doing the incorrect > detection. > > Alex > > Sent from my iPhone 5 > > > On 16 Jul 2014, at 18:18, Thomas Watson wrote: > > > > 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 > > > > > > Ji Hoon Baik ---07/16/2014 11:32:19 AM---Gents, Any help > will be much appreciated on this matter. > > > > From: Ji Hoon Baik > > 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
Re: [equinox-dev] 32bit vs 64bit launcher
You might find that a wow64 launch of Eclipse 32 should work, but to do so needs to know its in 32 bit mode. I believe that the auto detection will still think it's in 64 bit mode even with 32 bit wow and so the 32 bit launcher looks for the 64 bit library and then fails to load or not find it. You may find running with -Dosgi.arch=x86 will allow you to launch as 32bit depending on which part of the process is doing the incorrect detection. Alex Sent from my iPhone 5 > On 16 Jul 2014, at 18:18, Thomas Watson wrote: > > 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 > > > Ji Hoon Baik ---07/16/2014 11:32:19 AM---Gents, Any help will be > much appreciated on this matter. > > From: Ji Hoon Baik > 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 ___ 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
Re: [equinox-dev] 32bit vs 64bit launcher
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 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
