 AIX7.1/Eclipse4.4.2 X Window System Error [message #1429760] |
Tue, 23 September 2014 18:11  |
 JD Johnson
Messages: 1
Registered: September 2014 |
Junior Member |
|
|
I downloaded and unzipped "eclipse-SDK-4.2.2-aix-gtk-ppc64.zip" to my AIX 7.1 system.
I ran into issues with XWindows (Exceed) and discovered the -nosplash. However, I am still experiencing an XWindows error upon starting eclipse.
Here is what I am entering on the command line.
./eclipse -vm /usr/java6_64/jre/bin/ -nosplash -debug
I get the "Workspace Launcher" screen. I hit OK to accept the default workspace. The "Workspace Launcher" screen disappears, and a box blips quickly on the screen for about 1/10th of a second, and the error is displayed, and I get my prompt back.
I have AIX 7.1, Exceed version 12, gtk2-2.10.6-5.
The debug output to the screen.
Start VM: -Xms40m
-Xmx512m
-Djava.class.path=/home/jjohnson/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-os aix
-ws gtk
-arch ppc64
-launcher /home/jjohnson/eclipse/eclipse
-name Eclipse
--launcher.library /home/jjohnson/eclipse//plugins/org.eclipse.equinox.launcher.gtk.aix.ppc64_1.1.100.v20120913-144808/eclipse_1502.so
-startup /home/jjohnson/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.overrideVmargs
-debug
-vm /usr/java6_64/jre/bin/j9vm/libjvm.so
-vmargs
-Xms40m
-Xmx512m
-Djava.class.path=/home/jjohnson/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
Install location:
file:/home/jjohnson/eclipse/
Configuration file:
file:/home/jjohnson/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/jjohnson/eclipse/configuration/
Framework located:
file:/home/jjohnson/eclipse/plugins/org.eclipse.osgi_3.8.2.v20130124-134944.jar
Framework classpath:
file:/home/jjohnson/eclipse/plugins/org.eclipse.osgi_3.8.2.v20130124-134944.jar
Debug options:
file:/home/jjohnson/eclipse/.options not found
Time to load bundles: 3
Starting application: 1205
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1617 error_code 3 request_code 42 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Here is the log from the ~/eclipse/configuration directory.
!SESSION 2014-09-23 09:41:51.022 -----------------------------------------------
eclipse.buildId=M20130204-1200
java.fullversion=JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr15-20131016_170922 (JIT enabled, AOT enabled)
J9VM - 20131016_170922
JIT - r9_20130920_46510ifx2
GC - GA24_Java6_SR15_20131016_1337_B170922
BootLoader constants: OS=aix, ARCH=ppc64, WS=gtk, NL=en_US
Command-line arguments: -os aix -ws gtk -arch ppc64 -debug
!ENTRY org.eclipse.osgi 4 0 2014-09-23 09:42:06.757
!MESSAGE Application error
!STACK 1
java.lang.IllegalArgumentException: Argument cannot be null
at org.eclipse.swt.SWT.error(SWT.java:4342)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at org.eclipse.swt.SWT.error(SWT.java:4247)
at org.eclipse.swt.widgets.Dialog.error(Dialog.java:198)
at org.eclipse.swt.widgets.Dialog.checkParent(Dialog.java:164)
at org.eclipse.swt.widgets.Dialog.<init>(Dialog.java:127)
at org.eclipse.swt.widgets.MessageBox.<init>(MessageBox.java:99)
at org.eclipse.ui.internal.ide.application.IDEApplication.checkValidWorkspace(IDEApplication.java:382)
at org.eclipse.ui.internal.ide.application.IDEApplication.promptForWorkspace(IDEApplication.java:338)
at org.eclipse.ui.internal.ide.application.IDEApplication.checkInstanceLocation(IDEApplication.java:238)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
I welcome any help you can provide.
[Updated on: Tue, 23 September 2014 22:28] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.06506 seconds
] 
Search
Help
Register
Login
Home
