[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-swt-dev] SWT - X Window System error Crash on Solaris (Sparc) 10u8 GTK / SWT 3.6.2 / JRE 1.6u24 (Silenio Quarti)
|
It seems as though the main reason the program is crashing is because
display = new Display()
Is not the first call in main.
Is it required to call Display() as the first line in main when using SWT_AWT Bridge, thus forcing you to place the SWT event loop inside of main?
I was planning on initializing Display/Running the SWT event loop in a separate "SWT" thread from main.
----------------------------------------
> From: jmandawg@xxxxxxxxxxx
> To: platform-swt-dev@xxxxxxxxxxx
> Subject: Re: SWT - X Window System error Crash on Solaris (Sparc) 10u8 GTK / SWT 3.6.2 / JRE 1.6u24 (Silenio Quarti)
> Date: Mon, 18 Apr 2011 13:13:41 -0400
>
>
> Here is the output of the Debug stacktrace:
>
>
> bash-3.00# java -cp .:solswt.jar CrashApp
> -------------------------------------------
> Entering SWT Display loop
>
> ---------------------------------------------
> org.eclipse.swt.SWTError: Unspecified error
> at org.eclipse.swt.graphics.Device.XErrorProc(Device.java:902)
> at sun.java2d.loops.DrawGlyphListAA.DrawGlyphListAA(Native Method)
> at sun.java2d.pipe.AATextRenderer.drawGlyphList(AATextRenderer.java:22)
> at sun.java2d.pipe.GlyphListPipe.drawString(GlyphListPipe.java:54)
> at sun.java2d.pipe.ValidatePipe.drawString(ValidatePipe.java:147)
> at sun.java2d.SunGraphics2D.drawString(SunGraphics2D.java:2753)
> at sun.swing.SwingUtilities2.drawString(SwingUtilities2.java:500)
> at sun.swing.SwingUtilities2.drawStringUnderlineCharAt(SwingUtilities2.j ava:531)
> at javax.swing.plaf.basic.BasicLabelUI.paintEnabledText(BasicLabelUI.jav a:101)
> at javax.swing.plaf.basic.BasicLabelUI.paint(BasicLabelUI.java:162)
> at javax.swing.plaf.ComponentUI.update(ComponentUI.java:143)
> at javax.swing.JComponent.paintComponent(JComponent.java:752)
> at javax.swing.JComponent.paint(JComponent.java:1029)
> at javax.swing.JComponent.paintChildren(JComponent.java:862)
> at javax.swing.JComponent.paint(JComponent.java:1038)
> at javax.swing.JComponent.paintChildren(JComponent.java:862)
> at javax.swing.JComponent.paint(JComponent.java:1038)
> at javax.swing.JComponent.paintChildren(JComponent.java:862)
> at javax.swing.JComponent.paint(JComponent.java:1038)
> at javax.swing.JLayeredPane.paint(JLayeredPane.java:567)
> at javax.swing.JComponent.paintChildren(JComponent.java:862)
> at javax.swing.JComponent.paintToOffscreen(JComponent.java:5131)
> at javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManag er.java:278)
> at javax.swing.RepaintManager.paint(RepaintManager.java:1224)
> at javax.swing.JComponent.paint(JComponent.java:1015)
> at java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:21)
> at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java: 60)
> at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:97 )
> at java.awt.Container.paint(Container.java:1780)
> at java.awt.Window.paint(Window.java:3375)
> at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:796)
> at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:713)
> at javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java:6 93)
> at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(System EventQueueUtilities.java:125)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:642)
> at java.awt.EventQueue.access$000(EventQueue.java:85)
> at java.awt.EventQueue$1.run(EventQueue.java:603)
> at java.awt.EventQueue$1.run(EventQueue.java:601)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessCo ntrolContext.java:87)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:612)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre ad.java:269)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread. java:184)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre ad.java:174)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
> The program 'SWT' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
> (Details: serial 687 error_code 8 request_code 129 minor_code 4)
> (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.)
> bash-3.00#
>
>
>
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 18 Apr 2011 10:50:42 -0400
> > From: Silenio Quarti
> > To: "Eclipse Platform SWT component developers list."
> >
> > Subject: Re: [platform-swt-dev] SWT - X Window System error Crash on
> > Solaris (Sparc) 10u8 GTK / SWT 3.6.2 / JRE 1.6u24
> > Message-ID:
> >
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Try setting
> >
> > Display.DEBUG=true;
> >
> > in the first line of your main method. It should show the stack when the
> > BadMatch error happen.
> >
> > Silenio
> >
> >
> >
>
>
