Home » Newcomers » Newcomers » Eclipse 3.3.1 crashes on launch
|
| Re: Eclipse 3.3.1 crashes on launch [message #247356 is a reply to message #247351] |
Thu, 31 January 2008 21:20   |
Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"rektide" <rektide@gmail.com> wrote in message
news:ad1293be8bd65280861601e3e46f2f6b$1@www.eclipse.org...
> I posted this problem in a different forum and it disappeared. Probably
> my mistake but it was rather irksome looking for something that
> mysteriously vanished.
Your original post is still visible to me, using Outlook Express, in
eclipse.platform.
I don't have an answer for you, though, other than "try specifying the VM
explicitly on the Eclipse command line, and see if that helps."
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247360 is a reply to message #247356] |
Thu, 31 January 2008 21:48 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------090204090005090206080802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Walter,
I assume he didn't unzip over top of an older install since that's
likely not to work well...
Walter Harley wrote:
> "rektide" <rektide@gmail.com> wrote in message
> news:ad1293be8bd65280861601e3e46f2f6b$1@www.eclipse.org...
>
>> I posted this problem in a different forum and it disappeared. Probably
>> my mistake but it was rather irksome looking for something that
>> mysteriously vanished.
>>
>
> Your original post is still visible to me, using Outlook Express, in
> eclipse.platform.
>
> I don't have an answer for you, though, other than "try specifying the VM
> explicitly on the Eclipse command line, and see if that helps."
>
>
>
--------------090204090005090206080802
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Walter,<br>
<br>
I assume he didn't unzip over top of an older install since that's
likely not to work well...<br>
<br>
<br>
Walter Harley wrote:
<blockquote cite="mid:fnte3o$i3a$1@build.eclipse.org" type="cite">
<pre wrap="">"rektide" <a class="moz-txt-link-rfc2396E" href="mailto:rektide@gmail.com"><rektide@gmail.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:ad1293be8bd65280861601e3e46f2f6b$1@www.eclipse.org">news:ad1293be8bd65280861601e3e46f2f6b$1@www.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I posted this problem in a different forum and it disappeared. Probably
my mistake but it was rather irksome looking for something that
mysteriously vanished.
</pre>
</blockquote>
<pre wrap=""><!---->
Your original post is still visible to me, using Outlook Express, in
eclipse.platform.
I don't have an answer for you, though, other than "try specifying the VM
explicitly on the Eclipse command line, and see if that helps."
</pre>
</blockquote>
<br>
</body>
</html>
--------------090204090005090206080802--
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247384 is a reply to message #247360] |
Thu, 31 January 2008 23:36 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:fntfoq$hjt$3@build.eclipse.org...
>I assume he didn't unzip over top of an older install since that's likely
>not to work well...
Good point! His path suggests that might be what happened.
I swear, given all the questions like this that we answer on these
newsgroups, I really wonder about the wisdom of not having an installer - at
least something that could reliably unpack, check for the existence of a
reasonable JRE, check path limitations, and check that the app isn't being
installed on top of an old install. Maybe p2 does all that, but I think
there is still a bootstrapping problem.
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247395 is a reply to message #247384] |
Fri, 01 February 2008 01:23 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------070507010800000609070506
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Walter,
I know. I think that as you get experienced you almost build up implicit
problem correcting steps that you might forget to spell out: like use
-clean, install in a fresh new location, or erase the old one first.
Then again who would erase the old one first; what if the new one
doesn't work! :-) My solution is: install a new Eclipse every couple
of weeks so I don't forget all the steps. Of course that's fine as
someone working on the latest stream walking forward in lock step with
the platform, but it's not realistic for users. Update manager seems
like a nightmare from hell, though I've never used it myself; but
apparently EMF is installed that way far more frequently than via people
unzipping zip files. I guess P2 will be a panacea. I can only hope. I
do have confidence in the people who say it will be good...
Walter Harley wrote:
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:fntfoq$hjt$3@build.eclipse.org...
>
>> I assume he didn't unzip over top of an older install since that's likely
>> not to work well...
>>
>
> Good point! His path suggests that might be what happened.
>
> I swear, given all the questions like this that we answer on these
> newsgroups, I really wonder about the wisdom of not having an installer - at
> least something that could reliably unpack, check for the existence of a
> reasonable JRE, check path limitations, and check that the app isn't being
> installed on top of an old install. Maybe p2 does all that, but I think
> there is still a bootstrapping problem.
>
>
>
--------------070507010800000609070506
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Walter,<br>
<br>
I know. I think that as you get experienced you almost build up
implicit problem correcting steps that you might forget to spell out:
like use -clean, install in a fresh new location, or erase the old one
first. Then again who would erase the old one first; what if the new
one doesn't work! :-) My solution is: install a new Eclipse every
couple of weeks so I don't forget all the steps. Of course that's fine
as someone working on the latest stream walking forward in lock step
with the platform, but it's not realistic for users. Update manager
seems like a nightmare from hell, though I've never used it myself; but
apparently EMF is installed that way far more frequently than via
people unzipping zip files. I guess P2 will be a panacea. I can only
hope. I do have confidence in the people who say it will be good...<br>
<br>
<br>
<br>
Walter Harley wrote:
<blockquote cite="mid:fntm12$gm$1@build.eclipse.org" type="cite">
<pre wrap="">"Ed Merks" <a class="moz-txt-link-rfc2396E" href="mailto:merks@ca.ibm.com"><merks@ca.ibm.com></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fntfoq$hjt$3@build.eclipse.org">news:fntfoq$hjt$3@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I assume he didn't unzip over top of an older install since that's likely
not to work well...
</pre>
</blockquote>
<pre wrap=""><!---->
Good point! His path suggests that might be what happened.
I swear, given all the questions like this that we answer on these
newsgroups, I really wonder about the wisdom of not having an installer - at
least something that could reliably unpack, check for the existence of a
reasonable JRE, check path limitations, and check that the app isn't being
installed on top of an old install. Maybe p2 does all that, but I think
there is still a bootstrapping problem.
</pre>
</blockquote>
<br>
</body>
</html>
--------------070507010800000609070506--
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247428 is a reply to message #247384] |
Fri, 01 February 2008 15:54 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Walter Harley wrote:
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:fntfoq$hjt$3@build.eclipse.org...
>> I assume he didn't unzip over top of an older install since that's likely
>> not to work well...
>
> Good point! His path suggests that might be what happened.
>
> I swear, given all the questions like this that we answer on these
> newsgroups, I really wonder about the wisdom of not having an installer - at
> least something that could reliably unpack, check for the existence of a
> reasonable JRE, check path limitations, and check that the app isn't being
> installed on top of an old install. Maybe p2 does all that, but I think
> there is still a bootstrapping problem.
At its inception, creating an installer was one of the goals of the
Packaging project (EPP) - see http://www.eclipse.org/epp/
But the newsgroup for EPP has been silent for a long time except for a
recent announcement that early-access Ganymede packages are available.
There was a flurry of activity around the installer early on in EPP but
I haven't seen any reference to progress in quite a while.
Eric
|
|
| | |
| Re: Eclipse 3.3.1 crashes on launch [message #247798 is a reply to message #247395] |
Mon, 04 February 2008 21:42 |
 rektide
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Ed Merks wrote:
> Walter,
> I know. I think that as you get experienced you almost build up implicit
> problem correcting steps that you might forget to spell out: like use
> -clean, install in a fresh new location, or erase the old one first.
> Then again who would erase the old one first; what if the new one
> doesn't work! :-) My solution is: install a new Eclipse every couple
> of weeks so I don't forget all the steps. Of course that's fine as
> someone working on the latest stream walking forward in lock step with
> the platform, but it's not realistic for users. Update manager seems
> like a nightmare from hell, though I've never used it myself; but
> apparently EMF is installed that way far more frequently than via people
> unzipping zip files. I guess P2 will be a panacea. I can only hope. I
> do have confidence in the people who say it will be good...
Indeed I havent found any instructions for installing besides un-tar-gz,
cd, ./eclise. Even just making a page with something more helpful than
"unzip, run", one that covers problem cases, would probably be a good
start.
More problematically, when eclispe doesnt run, it doesnt give you any idea
what went wrong: the error messages for failed launch are completely
useless. I suspect if there were more instructive errors about what
failed, people would be a lot better able to trouble shoot on their. I
dont see any reason why eclispe cant throw some kind of error, rather than
an error code.
Update manager has always worked fine for my plugins.
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247801 is a reply to message #247798] |
Mon, 04 February 2008 22:32 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
rektide wrote:
> Ed Merks wrote:
>
>> Walter,
>
>> I know. I think that as you get experienced you almost build up
>> implicit problem correcting steps that you might forget to spell out:
>> like use -clean, install in a fresh new location, or erase the old one
>> first. Then again who would erase the old one first; what if the new
>> one doesn't work! :-) My solution is: install a new Eclipse every
>> couple of weeks so I don't forget all the steps. Of course that's
>> fine as someone working on the latest stream walking forward in lock
>> step with the platform, but it's not realistic for users. Update
>> manager seems like a nightmare from hell, though I've never used it
>> myself; but apparently EMF is installed that way far more frequently
>> than via people unzipping zip files. I guess P2 will be a panacea. I
>> can only hope. I do have confidence in the people who say it will be
>> good...
>
> Indeed I havent found any instructions for installing besides un-tar-gz,
> cd, ./eclise. Even just making a page with something more helpful than
> "unzip, run", one that covers problem cases, would probably be a good
> start.
>
> More problematically, when eclispe doesnt run, it doesnt give you any
> idea what went wrong: the error messages for failed launch are
> completely useless. I suspect if there were more instructive errors
> about what failed, people would be a lot better able to trouble shoot on
> their. I dont see any reason why eclispe cant throw some kind of error,
> rather than an error code.
A link to this page is featured on the Downloads page:
http://wiki.eclipse.org/SDK_Known_Issues
If it is the JVM that is crashing there is nothing Eclipse can do.
Eric
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247807 is a reply to message #247801] |
Mon, 04 February 2008 22:52 |
rektide
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
>> Indeed I havent found any instructions for installing besides un-tar-gz,
>> cd, ./eclise. Even just making a page with something more helpful than
>> "unzip, run", one that covers problem cases, would probably be a good
>> start.
>>
>> More problematically, when eclispe doesnt run, it doesnt give you any
>> idea what went wrong: the error messages for failed launch are
>> completely useless. I suspect if there were more instructive errors
>> about what failed, people would be a lot better able to trouble shoot on
>> their. I dont see any reason why eclispe cant throw some kind of error,
>> rather than an error code.
> A link to this page is featured on the Downloads page:
> http://wiki.eclipse.org/SDK_Known_Issues
A link to what page?
I dont see anything on there that pertains to my issue. I'm not running
with gcj and the "unzip and run" did not work.
> If it is the JVM that is crashing there is nothing Eclipse can do.
How about reporting the error the JVM tosses? (although frankly being
able to run on linux amd64 sun java6 doesnt seem outlandishly unreasonable
to me)
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247811 is a reply to message #247807] |
Tue, 05 February 2008 00:45 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"rektide" <rektide@gmail.com> wrote in message
news:81fbce5a1a7b5d635635920066d26aaf$1@www.eclipse.org...
>> If it is the JVM that is crashing there is nothing Eclipse can do.
>
> How about reporting the error the JVM tosses? (although frankly being
> able to run on linux amd64 sun java6 doesnt seem outlandishly unreasonable
> to me)
It did. It reported "exit code 13".
Apparently no one here knows what that means: that's a Sun error code, not
an Eclipse error code. Perhaps Sun has some documentation on what their
error codes mean?
The Eclipse launcher is a very thin layer of C code, that starts up a JVM
and attempts to run a very thin layer of Java code, that puts up a splash
screen and starts up the rest of Eclipse. If that initial JVM launch fails
there is very little information to go on beyond what the JVM reports; and
you're seeing what the JVM reported, I think.
If you haven't already, try launching eclipsec.exe rather than eclipse.exe.
If the JVM spit stuff to the console as it was dying, you might be able to
see it that way.
|
|
|
| Re: Eclipse 3.3.1 crashes on launch [message #247893 is a reply to message #247807] |
Tue, 05 February 2008 14:03 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
rektide wrote:
>>> Indeed I havent found any instructions for installing besides
>>> un-tar-gz, cd, ./eclise. Even just making a page with something more
>>> helpful than "unzip, run", one that covers problem cases, would
>>> probably be a good start.
>>>
>>> More problematically, when eclispe doesnt run, it doesnt give you any
>>> idea what went wrong: the error messages for failed launch are
>>> completely useless. I suspect if there were more instructive errors
>>> about what failed, people would be a lot better able to trouble shoot
>>> on their. I dont see any reason why eclispe cant throw some kind of
>>> error, rather than an error code.
>
>> A link to this page is featured on the Downloads page:
>> http://wiki.eclipse.org/SDK_Known_Issues
>
> A link to what page?
> I dont see anything on there that pertains to my issue. I'm not running
> with gcj and the "unzip and run" did not work.
You said:
"Even just making a page with something more helpful than "unzip, run",
one that covers problem cases, would probably be a good start."
I responded with the Known Issues page that covers, surprisingly, known
issues with running Eclipse. The issue you see is obviously not in that
category (or at least something about your system/environment is not in
the category of "known problem"), but I was just letting you know that
there is a page along the lines of what you were asking for.
Also, don't forget that Eclipse is open source, including the wiki; so
please do contribute to that page, if appropriate, when you find the
cause of the problem you are experiencing.
Eric
|
|
|
Goto Forum:
Current Time: Fri Dec 27 03:03:52 GMT 2024
Powered by FUDForum. Page generated in 0.07926 seconds |
] 
Search
Help
Register
Login
Home
