Bug 222757 - Crashes under Linux amd64 when changing a project build path
Summary: Crashes under Linux amd64 when changing a project build path
Status: RESOLVED DUPLICATE of bug 214092
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-14 10:55 EDT by Tom Nichols CLA
Modified: 2009-10-01 09:36 EDT (History)
1 user (show)

See Also:


Attachments
crash log (146.48 KB, text/plain)
2008-03-14 10:55 EDT, Tom Nichols CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Nichols CLA 2008-03-14 10:55:22 EDT
Created attachment 92576 [details]
crash log

Build ID: M20080221-1800

Steps To Reproduce:
Changing a project's build path in any way causes Eclipse to immediately crash when the compiler kicks in.  

i.e.
- Right click on a JAR in a project, select "Add to build path"

or...

- Project-> properties -> build path -> (add/ remove any JAR Library, etc.).  Then close properties dialog

*crash*

More information:
Ubuntu 7.10 Gutsy on AMD64.  Running the Eclipse linux-64 build.  Sun Java SE 1.6.0_04 for linux x64.  Will attach the error log file.

Sometimes after I try to restart Eclipse will continually crash on startup until I manually remove the last change from the modified .classpath.

Apologies if this is a dup, I searched and couldn't find anything relating to changing the build path.
Comment 1 Remy Suen CLA 2008-03-14 12:35:18 EDT
Please see bug 214092.

Please run Eclipse on a 1.5 JRE, if you want 1.6, you should try 1.6.0.02 or 1.6.0.03.
Comment 2 Tom Nichols CLA 2008-03-14 16:23:50 EDT
Thanks; again sorry for the dup.  I'll be more diligent about posting in the forums before filing a new bug report.

*** This bug has been marked as a duplicate of bug 214092 ***
Comment 3 Remy Suen CLA 2008-03-14 16:26:26 EDT
(In reply to comment #2)
> Thanks; again sorry for the dup.  I'll be more diligent about posting in the
> forums before filing a new bug report.

Nothing to apologize for. It is often hard to find duplicates. Good luck with your problem and I hope using another JRE will solve it for you.