Community
Participate
Working Groups
Using Eclipse C/C++, Downloaded from the web as the source file (Not installed from repository), running on Debian based Linux (Linux Mint). Problem: The IDE (Eclipse) automatically closes. I use Alt+Tab a lot in order to switch between windows. Mostly when i switch from Eclipse to something else the IDE just closes by itself, losing all the modifications. For instance; I create a C source file and I switch to a pdf file to read something. Then I go back to IDE and write code, after a couple of switching the IDE just closes by itself, resulting in losing all the code that I've written in the source file. This happens not all the time but often, as i worked with Eclipse often lately. The closing problem also sometimes happened during the code edit. I open the IDE, to edit a C file. During my work (without switching between windows) the IDE shutsdown, and i lose all data. This happens less often than when i switch. Almost everytime that i use Alt+Tab, the IDE shutsdown automatically. -- Configuration Details -- Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.cpp.product) Installed Features: org.eclipse.platform 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L
You need to provide more details: What JVM are you using? What platform is this on? Please attach the produced JVM crashlog & workspace .metadata/.log.
(In reply to comment #1) > You need to provide more details: > What JVM are you using? > What platform is this on? > Please attach the produced JVM crashlog & workspace .metadata/.log. I don't know how i would do that, please guide me: tell me how i can find my JVM? and where i can find the produced JVM crashlog, and I'll gladly give you those information.
Usually there's an error log in the directory you ran eclipse from. It'll depend on how you're running eclipse, your JVM and your platform. Very likely if your eclipse is 'disappearing' the JVM is crashing. I'd bet it's this bug: bug 333227. AFAIK there aren't currently any known bugs in CDT itself that would cause this. If you can provide more details, and you're not using Oracle JVM 1.6.0_23/24 on x86_64, then reopen.
