Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » EXIT 13(Seems to have trouble with Eclipse.ini)
EXIT 13 [message #988425] Thu, 29 November 2012 20:49 Go to next message
Alvin Schmitt is currently offline Alvin Schmitt
Messages: 4
Registered: September 2012
Junior Member
I have read and downloaded the eclipse.ini wiki and read the related material. I posted a message on this on 9/7/2012 but got no email reply. I am still having problems with the exit 13 message. My path to javaw.exe is correct and on the line below -vm. I get t he following message which I was unable to copy and had to type in by hand. It is:

Java was started but returned exit code=13
C:\Program Files (x86)\java\jre7\bin\javaw.exe
-Dosgi.requiredJavaVersion=1.7
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx1024m
-XX:MaxPermSize=256m
-jar C:\Program
Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-os win32
-ws win32
-arch x86_64
-showsplash C:\Program
Files\eclipse\\plugins\org.eclipse.platform_4.2.0.v201206081400\splash.bmp
-launcher C:\program files\eclipse\eclipse.exe
-name Eclipse
--launcher.library C:\Program
Files\eclipse\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v2
0120522-1813\eclipse_1503.dll
-startup C:\Program
Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.overrideVmargs
-exitdata 12d0_58
-product org.eclipse.epp.package.cpp.product
-vm C:\Program Files (x86)\java\jre7\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx1024m
-XX:MaxPermSize=256m
-jar C:\Program
Files\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar

I tried - -Dosgi.requiredJavaVersion=1.5 and -Dosgi.requiredJavaVersion=1.7 with no luck Any ideas? Thanks. Alvin....
Re: EXIT 13 [message #988429 is a reply to message #988425] Thu, 29 November 2012 21:06 Go to previous messageGo to next message
Russell Bateman is currently offline Russell Bateman
Messages: 3231
Registered: July 2009
Location: Provo, Utah, USA
Senior Member

On 11/29/2012 1:49 PM, Alvin Schmitt wrote:
> I have read and downloaded the eclipse.ini wiki and read the related
> material. I posted a message on this on 9/7/2012 but got no email reply.
> I am still having problems with the exit 13 message. My path to
> javaw.exe is correct and on the line below -vm. I get t he following
> message which I was unable to copy and had to type in by hand. It is:
>
> Java was started but returned exit code=13
> C:\Program Files (x86)\java\jre7\bin\javaw.exe
> [snip]
> Files\eclipse\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v2
> [snip]

Any chance you're trying to run 64-bit Eclipse download on a 32-bit JRE?
Re: EXIT 13 [message #988650 is a reply to message #988425] Fri, 30 November 2012 21:28 Go to previous messageGo to next message
Steve Blass is currently offline Steve Blass
Messages: 276
Registered: July 2009
Senior Member
C:\Program Files\eclipse ?

Moving your eclipse folder to a path with no spaces might make a difference.
Re: EXIT 13 [message #988691 is a reply to message #988429] Sat, 01 December 2012 11:14 Go to previous messageGo to next message
Alvin Schmitt is currently offline Alvin Schmitt
Messages: 4
Registered: September 2012
Junior Member
I will look into that - also will put it in a path with no spaces. Thanks.
Re: EXIT 13 [message #988750 is a reply to message #988691] Sun, 02 December 2012 17:25 Go to previous messageGo to next message
Helmut Stettmaier is currently offline Helmut Stettmaier
Messages: 2
Registered: December 2012
Junior Member
Hello,
same problem for me, perhaps even worse as I use Windows 8...

I'm certain that my Java is a 64-Bit version although eclipse is the first thing to check this.
I also think that I installed the 64-Bit-Version of eclipse... OOPS, the name of the zipfile is "eclipse-cpp-juno-SR1-win32-x86_64.zip" - confusing...
I got this download via the link "Windows 64 Bit".

I did move the jre from "C:\Programme (x86)\Java\.." to "C:\Java\..." and this was the point where I discovered that no environment variable JAVAHOME or else was to be updated.

I also specified the jre: at first time as a parameter -vm ... for the call of eclipse.exe and secondly in eclipse.ini:
-vm
C:\Java\jre7\bin\javaw.exe

The problem was the same, "Java was started but returned exit code=13" and the rest of the message looks similar to that what Alvin reported.

This thread does not contain a solution but, Alvin, you have possibly got one as you don't insist any more - is there any other thread which I haven't discovered (I did search, but I'm by far not really good in this)?
Or can any of the reported odd things help finding the solution?

Thank you in advance and kind regards,
Helmut
Re: EXIT 13 [message #988764 is a reply to message #988750] Mon, 03 December 2012 03:11 Go to previous messageGo to next message
Russell Bateman is currently offline Russell Bateman
Messages: 3231
Registered: July 2009
Location: Provo, Utah, USA
Senior Member

On 12/02/2012 12:17 PM, Helmut Stettmaier wrote:
> Hello,
> same problem for me, perhaps even worse as I use Windows 8...
>
> I'm certain that my Java is a 64-Bit version although eclipse is the
> first thing to check this.
> I also think that I installed the 64-Bit-Version of eclipse... OOPS, the
> name of the zipfile is "eclipse-cpp-juno-SR1-win32-x86_64.zip" -
> confusing...
> I got this download via the link "Windows 64 Bit".
>
> I did move the jre from "C:\Programme (x86)\Java\.." to "C:\Java\..."
> and this was the point where I discovered that no environment variable
> JAVAHOME or else was to be updated.

Moving the 32-bit JRE from C:\Program (x86)\Java\... to anywhere else
won't transform it into a 64=bit JRE.

>
> I also specified the jre: at first time as a parameter -vm ... for the
> call of eclipse.exe and secondly in eclipse.ini:
> -vm
> C:\Java\jre7\bin\javaw.exe
>
> The problem was the same, "Java was started but returned exit code=13"
> and the rest of the message looks similar to that what Alvin reported.
>
> This thread does not contain a solution but, Alvin, you have possibly
> got one as you don't insist any more - is there any other thread which I
> haven't discovered (I did search, but I'm by far not really good in this)?
> Or can any of the reported odd things help finding the solution?
>
> Thank you in advance and kind regards,
> Helmut

It's not mysterious; I've never failed to get Eclipse running.

1. Download Sun Java JRE (or a JDK if you're going to develop in Java)
of proper bittedness for your hardware/OS. If in doubt or you just want
to be sure (it's the smart thing to do anyway), explode the JDK
privately--leave your system JRE alone.
2. Download appropriate Eclipse package for what you want to do of
proper bittedness to match the JRE you just got.
3. Modify eclipse.ini per http://wiki.eclipse.org/Eclipse.ini to wire it
up to the JRE/JDK you just downloaded.
4. Launch Eclipse.
5. Enjoy developing.
icon7.gif  Re: EXIT 13 [message #988838 is a reply to message #988764] Mon, 03 December 2012 12:06 Go to previous messageGo to next message
Helmut Stettmaier is currently offline Helmut Stettmaier
Messages: 2
Registered: December 2012
Junior Member
Hello Russel,
thank you for the quick response.

"Moving the 32-bit JRE from C:\Program (x86)\Java\... to anywhere else won't transform it into a 64=bit JRE."
Yes. And, of course, I thought (was sure), I have 64-Bit-Java, it was downloaded and installed freshly. Now it is.
The problem is that I had downloaded it online; finally I found a hint, that online download for java-64 is not possible, offline download is mandatory. I didn't be warned the first time. Frustrating.

C:\Java\jre7\bin>java -version
java version "1.7.0_09"
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)

"64-Bit Server VM" has replaced "Client VM" and obviously is essential.


This might be of interest for other newcomers finding a thread addressing exit code 13.


I wasn't sure about the bitnes of --> eclipse as the names of the zipfiles are confusing:
Klicking on Download "Windows 32 Bit" yields a zip file named "eclipse-cpp-juno-SR1-win32.zip".
Klicking on Download "Windows 64 Bit" yields a zip file named "eclipse-cpp-juno-SR1-win32-x86_64.zip", the name contains a "win32". But let us believe that it is a 64-Bit-version and I installed this one.
Perhaps a hint on the download page could help?

"I've never failed to get Eclipse running."
This makes me take courage... Eclipse now at least asks for a workspace... can't find EGit (I don't use it for the moment)... wants HOME to be defined (later)... and starts up. Let's face the other challenges :-D
Thank you very much!
Kind regards,
Helmut
Re: EXIT 13 [message #988873 is a reply to message #988838] Mon, 03 December 2012 14:11 Go to previous messageGo to next message
Russell Bateman is currently offline Russell Bateman
Messages: 3231
Registered: July 2009
Location: Provo, Utah, USA
Senior Member

On 12/03/2012 05:06 AM, Helmut Stettmaier wrote:
> Hello Russel,
> thank you for the quick response.
>
> "Moving the 32-bit JRE from C:\Program (x86)\Java\... to anywhere else
> won't transform it into a 64=bit JRE."
> Yes. And, of course, I thought (was sure), I have 64-Bit-Java, it was
> downloaded and installed freshly. Now it is.
> The problem is that I had downloaded it online; finally I found a hint,
> that online download for java-64 is not possible, offline download is
> mandatory. I didn't be warned the first time. Frustrating.
>
> C:\Java\jre7\bin>java -version
> java version "1.7.0_09"
> Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
>
> "64-Bit Server VM" has replaced "Client VM" and obviously is essential.
>
>
> This might be of interest for other newcomers finding a thread
> addressing exit code 13.
>
>
> I wasn't sure about the bitnes of --> eclipse as the names of the
> zipfiles are confusing:
> Klicking on Download "Windows 32 Bit" yields a zip file named
> "eclipse-cpp-juno-SR1-win32.zip".
> Klicking on Download "Windows 64 Bit" yields a zip file named
> "eclipse-cpp-juno-SR1-win32-x86_64.zip", the name contains a "win32".
> But let us believe that it is a 64-Bit-version and I installed this one.
> Perhaps a hint on the download page could help?
>
> "I've never failed to get Eclipse running."
> This makes me take courage... Eclipse now at least asks for a
> workspace... can't find EGit (I don't use it for the moment)... wants
> HOME to be defined (later)... and starts up. Let's face the other
> challenges :-D
> Thank you very much!
> Kind regards,
> Helmut

Yes, I suppose they could eliminate win32 from the name. Win32 is an
architecture, one that persists even into a 64-bit version, but it
doesn't designate the width. As I say, it could be eliminated because
we're way over a decade past needing to make the distinction from win16.

The eGit question must arise from your C/C++ download; you might ask in
the Eclipse CDT forum. I have no experience in that package. After 25+
years of C/asm, I moved to Eclipse and Java over 5 years ago and have
rarely looked back since, only for employers that needed my help and
then I only used good ol' Make and gcc, but I'm confident that Eclipse
CDT must rock 'cause everything Eclipse does pretty well rocks!
Re: EXIT 13 [message #988942 is a reply to message #988429] Mon, 03 December 2012 22:22 Go to previous message
Alvin Schmitt is currently offline Alvin Schmitt
Messages: 4
Registered: September 2012
Junior Member
You were right! when I changed from Program Files (x86) which is 32 bit to Program Files Java which is 64 bit Eclipse worked!. Note that Eclipse set up the ini file that pointed to the wrong (32 bit) version of java.
Previous Topic:Problems creating Java Project from Existing Ant Buildfile
Next Topic:Debugging jBC
Goto Forum:
  


Current Time: Thu Oct 30 14:42:34 GMT 2014

Powered by FUDForum. Page generated in 0.05807 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software