Eclipse Community Forums: Standard Widget Toolkit (SWT)

Help

Home

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » BadGC in AIX Motif

Show: Today's Messages :: Show Polls :: Message Navigator

BadGC in AIX Motif [message #464201]

Fri, 18 November 2005 16:40

Mike Tabb

Messages: 24
Registered: July 2009

Junior Member

Currently in my app when I open a few dialogs and cancel them , I get:
X Error of failed request: BadGC (invalid GC parameter)
Major opcode of failed request: 56 (XChangeGC)
Resource id in failed request: 0x360b729c

The same app runs on windows fine and does not leak. It seems to be
happening in the MOtif layer , but it is hard to debug. The correct patches
are applied to the aix system that eclipse requires.

Report message to a moderator

Re: BadGC in AIX Motif [message #464231 is a reply to message #464201]

Fri, 18 November 2005 20:04

Steve Northover

Messages: 1636
Registered: July 2009

Senior Member

You need the amazing Device.DEBUG flag that does an XSynchronize() and
prints a stack trace when an X error occurs. Set this thing to true before
creating the Display. The problem is most likely in SWT so be sure to enter
a bug report with the stack trace when you are done. Good luck!

"Mike Tabb" <mtabb@us.ibm.com> wrote in message
news:dll06s$sl6$1@news.eclipse.org...
> Currently in my app when I open a few dialogs and cancel them , I get:
> X Error of failed request: BadGC (invalid GC parameter)
> Major opcode of failed request: 56 (XChangeGC)
> Resource id in failed request: 0x360b729c
>
> The same app runs on windows fine and does not leak. It seems to be
> happening in the MOtif layer , but it is hard to debug. The correct
patches
> are applied to the aix system that eclipse requires.
>
>

Report message to a moderator

Re: BadGC in AIX Motif [message #464241 is a reply to message #464231]

Fri, 18 November 2005 22:06

Mike Tabb

Messages: 24
Registered: July 2009

Junior Member

Thanks for the reply. I forgot to mention that this is on an RCP
application , and the dialogs are launched from within the app. The RCP app
then crashes after the dismissal of the second one. Since I don't have any
control over when the display is created , when would you suggest I turn the
DEBUG flag on , if still possible. Thanks in adavnace.
"Steve Northover" <steve_northover@ca.ibm.com> wrote in message
news:dllc41$d5p$1@news.eclipse.org...
> You need the amazing Device.DEBUG flag that does an XSynchronize() and
> prints a stack trace when an X error occurs. Set this thing to true
before
> creating the Display. The problem is most likely in SWT so be sure to
enter
> a bug report with the stack trace when you are done. Good luck!
>
> "Mike Tabb" <mtabb@us.ibm.com> wrote in message
> news:dll06s$sl6$1@news.eclipse.org...
> > Currently in my app when I open a few dialogs and cancel them , I get:
> > X Error of failed request: BadGC (invalid GC parameter)
> > Major opcode of failed request: 56 (XChangeGC)
> > Resource id in failed request: 0x360b729c
> >
> > The same app runs on windows fine and does not leak. It seems to be
> > happening in the MOtif layer , but it is hard to debug. The correct
> patches
> > are applied to the aix system that eclipse requires.
> >
> >
>
>

Report message to a moderator

Re: BadGC in AIX Motif [message #464795 is a reply to message #464241]

Wed, 30 November 2005 01:00

Steve Northover

Messages: 1636
Registered: July 2009

Senior Member

Do the instructions for the Sleak plugin for Eclipse apply?
http://eclipse.org/swt/tools.php

Try asking the question on eclipse.platform or eclipse.platform.rcp. That's
where these sorts of questions are answered.

"Mike Tabb" <mtabb@us.ibm.com> wrote in message
news:dllj8t$mlr$1@news.eclipse.org...
> Thanks for the reply. I forgot to mention that this is on an RCP
> application , and the dialogs are launched from within the app. The RCP
app
> then crashes after the dismissal of the second one. Since I don't have
any
> control over when the display is created , when would you suggest I turn
the
> DEBUG flag on , if still possible. Thanks in adavnace.
> "Steve Northover" <steve_northover@ca.ibm.com> wrote in message
> news:dllc41$d5p$1@news.eclipse.org...
> > You need the amazing Device.DEBUG flag that does an XSynchronize() and
> > prints a stack trace when an X error occurs. Set this thing to true
> before
> > creating the Display. The problem is most likely in SWT so be sure to
> enter
> > a bug report with the stack trace when you are done. Good luck!
> >
> > "Mike Tabb" <mtabb@us.ibm.com> wrote in message
> > news:dll06s$sl6$1@news.eclipse.org...
> > > Currently in my app when I open a few dialogs and cancel them , I get:
> > > X Error of failed request: BadGC (invalid GC parameter)
> > > Major opcode of failed request: 56 (XChangeGC)
> > > Resource id in failed request: 0x360b729c
> > >
> > > The same app runs on windows fine and does not leak. It seems to be
> > > happening in the MOtif layer , but it is hard to debug. The correct
> > patches
> > > are applied to the aix system that eclipse requires.
> > >
> > >
> >
> >
>
>

Report message to a moderator

Previous Topic:	ControlTransfer ?
Next Topic:	New data binding framework

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 00:37:52 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter