Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327691 - [launcher] Eclipse crashes on open
Summary: [launcher] Eclipse crashes on open
Status: RESOLVED INVALID
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-13 13:14 EDT by allen gordon CLA
Modified: 2010-10-13 14:52 EDT (History)
4 users (show)

See Also:

Attachments
backtrace of crash (14.51 KB, text/plain)
2010-10-13 13:22 EDT, allen gordon CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description allen gordon CLA 2010-10-13 13:14:52 EDT 
Build Identifier: eclipse-java-helios-SR1-linux-gtk (can't get build id)

I had an eclipse session open and had a power failure.  Reboot was normal.  Opening Eclipse resulted in a segmentation fault.  see attached

Reproducible: Always

Steps to Reproduce:
1.   open eclipse java session with some open files
2.   Power fail
3.   reboot
4.   open eclipse
Comment 1 allen gordon CLA 2010-10-13 13:22:28 EDT 
Created attachment 180798 [details]
backtrace of crash

package:  eclipse-platform-1:3.5.2-2.fc13
component: eclipse
executable: eclipse
cmdline: eclipse
arch: i686
kernel: 2.6.33..3-85.fc13.i686.PAE
Reason:  prose /usr/lib/eclipse was killed by siganl 11 (SIGSEGV)
Comment 2 Thomas Watson CLA 2010-10-13 14:12:16 EDT 
If you unzip the eclipse-java-helios-SR1-linux-gtk build into a new location does it launch correctly?
Comment 3 allen gordon CLA 2010-10-13 14:39:33 EDT 
MY BAD!!!!!   This is a non-issue.  For another project, I was using an older version of java (1.4.1_02) and absent mindedly put it in the path so this version was being used instead of the current version.  Eclipse did not like this version!!!  Sorry for the the alarm.

Allen
Comment 4 Andrew Niefer CLA 2010-10-13 14:52:30 EDT 
I didn't even notice the 1.4.1 in the trace.
Our JNI launching has been iffy on older vms, some portion of eclipse may run on 1.4.1, if you ever actually want to use that vm try running with "-vm /home/allgordo/bin/j2sdk1.4.1_02/jre/bin/java" which will start the vm in its own process instead of using the JNI invocation API.