User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.2 (like Gecko) Build Identifier: My Eclipse Crash with the message that I should look in the ~/workspace/.metadata/.log for more Information. The content I attached below. Many hours ago ;-) I located the Problem. The standard configuration of mountpoints with no specification seems to be noexec. This is a good thing against unintentional execution in my home directory. Now I must change this for Eclipse and it works fine. I don't know if native code must execute in my home directoy, but if there another way I would prefered it. Bye Reproducible: Always Steps to Reproduce: 1.Start Eclipse 3.2.1 Actual Results: My Eclipse Crash with the message that I should look in the ~/workspace/.metadata/.log for more Information. The content I attached below. Expected Results: Eclipse should start normally. Content of .log eclipse.buildId=M20060629-1905 java.version=1.5.0_08 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 2 1 2006-10-28 15:50:10.530 !MESSAGE NLS missing message: fileInitializer_missingFileName in: org.eclipse.core.internal.runtime.messages !ENTRY org.eclipse.osgi 4 0 2006-10-28 15:50:11.231 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: /home/pose/.eclipse/org.eclipse.platform_3.2.0/configuration/org.eclipse.osgi/bundles/55/1/.cp/libswt-pi-gtk-3232.so: /home/pose/.eclipse/org.eclipse.platform_3.2.0/configuration/org.eclipse.osgi/bundles/55/1/.cp/libswt-pi-gtk-3232.so: failed to map segment from shared object: Operation not permitted at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1660) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:993) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) at org.eclipse.swt.widgets.Display.<clinit>(Display.java:126) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:433) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161) at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:122) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:75) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
/home mounted noexec?
(In reply to comment #1) > /home mounted noexec? > Yes. I have a seperatly partition for /home. When in the /etc/fstab the option "exec" is not present, eclipse don't start, because the standard configuration is noexec. I think many people have a seperatly partition for /home. And I think all of these can't start eclipse in this Version, until they don't change the fstab configuration. Here the definition from the manpage: noexec - Do not allow direct execution of any binaries on the mounted file system. Eclipse is almost written in Java, but a little part of it is written in a OS dependent language. Because that Eclipse means: failed to map segment from shared object: Operation not permitted at java.lang.ClassLoader$NativeLibrary.load(Native Method) Eclipse makes a copy of the libswt-pi-gtk-3232.so in the home directory. I don't know why. I think Eclipse try to execute native code in the home directory. But this is not permited in the standard configuration. You know what I mean?
> The standard configuration of mountpoints with no specification seems to > to be noexec No, not really. Not a Gentoo-specific issue, if you think it's a bug, then report it upstream. https://bugs.eclipse.org/bugs/
David: Uh, I should actually read your bug report, instead just having a look at the error output. Didn't realize that you found the problem already. :) For Eclipse the problem is that it consists of bunch of jars and it can't load the libraries from inside of them. Don't know if Eclipse can be configured to pick up the libraries, if they were installed plain in the first place.
Like to hear maintainers voice. :)
This certainly looks like an upstream issue. Could you please file a bug upstream, and post a reference to it on this bug? After that, I can pass it along linux-distro mailing list for Eclipse (where we work on maintaining Eclipse on the various distros), as this is likely to be present on other distributions as well.
Sorry, now I see that is already posted a bug like this on the Eclipse Bugzilla. https://bugs.eclipse.org/bugs/show_bug.cgi?id=128485 It seems that the eclipse project is not interested to change that.
You may want to open a feature request, ie for a way to use eclipse with noexec mounted home dir, and make reference to that bug.
Closing, as it's an upstream problem. You may want to check Eclipse-3.3 but I believe the problem is still there since you mentioned upstream was not interested in implementing this feature.
(In reply to comment #9) > Closing, as it's an upstream problem. Then resolve it as that please.
Suffices when users resolve bug reports incorrectly.
