Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314036 - Eclipse IDE closes silently on expanding Debug/src item in Project Explorer
Summary: Eclipse IDE closes silently on expanding Debug/src item in Project Explorer
Status: RESOLVED WORKSFORME
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 7.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-23 03:28 EDT by olelukoie CLA
Modified: 2010-10-22 16:59 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description olelukoie CLA 2010-05-23 03:28:21 EDT
Build Identifier: 20100520-1308 (helios RC1)

When I try to expand Debug/src item of the current project in Project Explorer eclipse silently closes without any error messages or console output.

I've tested with Sun Java 1.6.0.20 and OpenJDK 1.6.0 b18

This bug appears to happen only on 64-bit system (x86_64) with 64-bit versions of Java and Eclipse. I have tested 32-bit version on 32-bit system with the same versions of java and have not seen this bug.

Reproducible: Always

Steps to Reproduce:
1. Open Eclipse IDE for C++ development and create new "Hello World C++ Project"
2. Try to expand Debug/src item of the project in Project Explorer
3.
Comment 1 Elena Laskavaia CLA 2010-05-23 10:01:10 EDT
This is JVM crash. You need to find a stack dump from it.
Comment 2 olelukoie CLA 2010-05-23 12:41:20 EDT
Sorry, I have no any experience in java developing/debugging and I don't know how to get this dump. It seems that JVM doesn't create it at all.

I've tried to run eclipse under gdb and after a crash it just told me that the "Program exited normally".

All I can see in the ~/workspace/.log file is this repeating text:

!SESSION 2010-05-23 20:29:42.374 -----------------------------------------------
eclipse.buildId=I20100513-1500
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=ru_RU
Framework arguments:  -product org.eclipse.epp.package.cpp.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.cpp.product

!ENTRY org.eclipse.core.resources 2 10035 2010-05-23 20:29:45.832
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

After I've tried to run eclipse with LC_ALL=C the only change I've seen is "NL=en_US" instead of "NL=ru_RU" in "BootLoader" line of this log.

I've also tried to add -verbose -ea -esa options but they hadn't changed anything in eclipse and JVM behaviour. Eclipse just silently closes.
Comment 3 olelukoie CLA 2010-06-14 15:29:05 EDT
Well, I've got core file. The problem with it's generation was ulimit because its size is almost 300 MiBs (using OpenJDK)!

So the only additional info I can currently provide is a gdb output:

$ gdb ./eclipse --core ./core.17304 
GNU gdb (GDB) 7.1-1mdv2010.1 (Mandriva Linux release 2010.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mandriva-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/olelukoie/eclipse/eclipse...done.

warning: core file may not match specified executable file.
[New Thread 17305]
[New Thread 17307]
[New Thread 17306]
[New Thread 17308]
[New Thread 17309]
[New Thread 17311]
[New Thread 17310]
[New Thread 17312]
[New Thread 17313]
[New Thread 17314]
[New Thread 17315]
[New Thread 17324]
[New Thread 17320]
[New Thread 17329]
[New Thread 17321]
[New Thread 17333]
[New Thread 17322]
[New Thread 17380]
[New Thread 17325]
[New Thread 17381]
[New Thread 17342]
[New Thread 17382]
[New Thread 17379]
[New Thread 17383]
[New Thread 17385]
[New Thread 17304]
[New Thread 17384]
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `/usr/bin/java -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx3'.
Program terminated with signal 6, Aborted.
#0  0x00007ffff726c925 in ?? ()
(gdb) bt full
#0  0x00007ffff726c925 in ?? ()
No symbol table info available.
#1  0x00007ffff726df40 in ?? ()
No symbol table info available.
#2  0x00000000042b0df0 in ?? ()
No symbol table info available.
#3  0x00007ffff7df34e5 in _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:41
No locals.
#4  0x00007fffc5df8806 in ?? ()
No symbol table info available.
#5  0x00000000041f1120 in ?? ()
No symbol table info available.
#6  0x00000000041f1120 in ?? ()
No symbol table info available.
#7  0x00000000042ac2b0 in ?? ()
No symbol table info available.
#8  0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)

Not much helpfull...
Comment 4 Elena Laskavaia CLA 2010-06-14 20:08:29 EDT
No it is usually printed somewhere on console... And it says which library is crashed. Core is not produce by "eclipse" binary but by java binary (stack stack trace is bogus)
Comment 5 olelukoie CLA 2010-08-25 15:07:53 EDT
After a couple of months and a lot of updates of both my system and eclipse I can not reproduce the bug any more so I close report for now. I would reopen it if the bug appears once again. Hope it won't be needed.
Comment 6 fbaudouin CLA 2010-10-22 16:59:24 EDT
I have the same effects on the same system, on same version of eclipse (both of helios version produce this crash).
I tried many jvm without any success (openJDK, sun 1.5, sun 1.6, JRockit, ...).
Currently, i have to stay in galileo version to keep eclipse working.
A can produce any log needed to look forward.