Community
Participate
Working Groups
Build ID: I20071101-2000 Steps To Reproduce: This launcher command no longer works: C:\Development\Eclipse\SDK\3.4M3\eclipse.exe -vm "C:\Programme\Java\jdk1.6.0\jre\bin\server\jvm.dll" -clean -vmargs -server -Xms256m -Xmx360m -XX:MaxPermSize=128m It was working with 3.3. When trying to start, I get the launcher error dialog that the JVM terminated with an exit code of 1. More information:
Reproduced on Gentoo Linux i386. rcjsuen@sola ~/eclipse $ ./eclipse -vm /opt/sun-jdk-1.6.0.02/jre/lib/i386/server/libjvm.so -clean -vmargs -server Unrecognized option: -server ./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java -clean -vmargs -server ./eclipse -vm /opt/sun-jdk-1.6.0.02/jre/lib/i386/server/libjvm.so -clean ./eclipse -vm /opt/sun-jdk-1.6.0.02/jre/lib/i386/server/libjvm.so -clean -vmargs -Xms256m -Xmx360m -XX:MaxPermSize=128m ...are all okay otherwise. For #3, I have verified that those vm arguments are getting passed properly to Eclipse via the 'Configuration Details' in the about dialog.
Worksforme when not using -server
Dupping this to bug 204009. The fix for bug 204009 will likely consume the -server and -client arguments since the java launchers (java.exe, javaw.exe) consume the argument and choose the correct dll and the argument is not passed to the dll. *** This bug has been marked as a duplicate of bug 204009 ***
As Tom said, this is a combination of bug 205990 and bug 204009. Arguments like -server and -client (-Xdock:icon and others on the mac) are interpreted by the java launcher itself and not by the vm. This means that the eclipse launcher either has to start consuming and recognizing such options or pass them through and the vm would not recognize them. As a side note, I thought that -server just served as a way to choose between actual jvms. Unless the java launcher is doing something I am not aware of (like adding extra vm arguments when -server is specified), pointing -vm at /server/jvm.dll makes -server unnecessary.
(In reply to comment #4) > As a side note, I thought that -server just served as a way to choose between > actual jvms. Unless the java launcher is doing something I am not aware of > (like adding extra vm arguments when -server is specified), pointing -vm at > /server/jvm.dll makes -server unnecessary. > Good question. I was under the impression java launcher used the -server/-client options to choose the correct jvm library to load. Is that what you mean by "choose between actual jvms"? Do you think simply searching for the library in the server directory when -server is used is good enough? That is what I was thinking.
Yes that is what I meant. I'm hoping that choosing the correct jvm library is sufficient. Currently the launcher has a list of relative locations in which to find libraries that we go through in the order they are listed in the source. I was hoping all we need to do there is associate an argument (-server, -client, -classic, etc) with each of those locations.
