|Indigo dies on start with JDK 1.7.0_40 from desktop, but not from cmd window [message #1107580]
||Thu, 12 September 2013 12:19
| David M. Karr
Registered: July 2009
Running latest SR of Indigo on Win7SP1.|
One thing that I find frustrating sometimes is that Eclipse sometimes fails immediately on startup with a "JVM startup" error. It gives me a dialog with the Java command line, and just says it exited with code 1.
Up to today, I was able to start Indigo from my desktop shortcut using JDK 1.70_25. This morning I changed my ini file to reference 1.7.0_40 and restarted it. It failed immediately with that JVM startup error. It doesn't even write anything into the workspace log file.
However, if I first run a Windows cmd and then just paste the contents of my shortcut, it's able to start up without error.
It would really be nice if I could get some better diagnostics when it fails.
Powered by FUDForum
. Page generated in 0.01870 seconds