Equinox Launcher Issues
This page outlines the current situation with the equinox launcher.
linux.ppc, linux.x86_64 and aix.ppc experience crashes with older vms, and therefore currently default to running java as a separate process. The following table outlines these platforms and their JNI launching status with different vms.
|Platform||Reference VM||Other tested VMs|
|gtk.linux.ppc||IBM-1.4.2sr7 - works|| IBM 1.5.0 jcldp32dev-20070105 works|
IBM 1.5.0 pxp32devifx-20060124 crashes
|gtk.linux.x86_64||Sun 5.0 Update 11 - not tested|| IBM 1.4.2 j9xa64142-20061124 works|
Sun 1.5.0_09-b02 server crashes
IBM 1.4.2 j9xa64142-20060120 crashes
|motif.aix.ppc|| IBM-1.5.0sr4 - fails |
"A file or directory in the path name does not exist."
The eclipse.exe is linked on windows as a GUI application, which means the OS does not automatically allocate a console for it. This causes us several console related problems. See bug 168726, bug 167310, and bug 173962. Exact behaviour depends on the specific vm.
By linking the eclipse executable as a console application, all the console problems are solved. There are 2 options:
- link eclipse.exe as a console application, The console will always come up, but can be torn down if not desired (it will always flash).
- link a separate eclipse.com executable as a console application. In a console, windows will run "eclipse.com" before "eclipse.exe" if someone types only "eclipse".
- *Do we brand eclipse.com with an icon
- *What happens with batch files, people may get consoles when they weren't expecting one.
|VM||Java IO to console||Native IO to console||Ctrl+Break in console||redirectable IO (eclipse -debug > debug.txt)|
|IBM 1.4.2 cn142ifx-20060209||No||Yes||crash||Yes|
|IBM 1.5.0 pwidevifx-20060124||Yes||Yes||Yes||No|
|Sun 1.4.2_12||No||Yes||No*||No - Ctrl+Break stack trace does redirect|
|Sun 1.5.0_07||Yes||Yes||No*||No - Ctrl+Break stack trace does redirect|
Swing Applications on MacOSX
Mac is the only platform that always runs the vm in-process. The launcher by always created the vm on the main thread. This was a problem for Swing. See bug 181698. An argument "--launcher.secondThread" was added for the Mac to enable Swing applications. SWT will not work with this argument specified.
Should we also support the old mode of forking the vm on the mac?