X Window System Error using SWT_AWT Bridge on Linux [message #444861] |
Thu, 21 October 2004 15:52 |
Eddie Galvez Messages: 103 Registered: July 2009 |
Senior Member |
|
|
Eclipse 3.0.1 on Linux.
We're writing an RCP app, with a few embedded Swing components. In
particular, one of our editors is a graphical canvas, in Swing. Our app can
be made to crash if you resize, minimize, maximize, switch perspectives,
etc. enough [that is, the crash is reached purely by playing around with the
widgets, not invoking any specific action]. An example error we get is:
The program '<unknown>' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 62694 error_code 8 request_code 73 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.)
Anything I can start doing to debug this problem?
Thank you!
|
|
|
Re: X Window System Error using SWT_AWT Bridge on Linux [message #445094 is a reply to message #444861] |
Mon, 25 October 2004 19:38 |
Steve Northover Messages: 1636 Registered: July 2009 |
Senior Member |
|
|
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=74095
"Eddie Galvez" <eddie@_nospam_grassybrook.com> wrote in message
news:cl8los$dci$1@eclipse.org...
> Eclipse 3.0.1 on Linux.
> We're writing an RCP app, with a few embedded Swing components. In
> particular, one of our editors is a graphical canvas, in Swing. Our app
can
> be made to crash if you resize, minimize, maximize, switch perspectives,
> etc. enough [that is, the crash is reached purely by playing around with
the
> widgets, not invoking any specific action]. An example error we get is:
>
> The program '<unknown>' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
> (Details: serial 62694 error_code 8 request_code 73 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.)
>
> Anything I can start doing to debug this problem?
>
> Thank you!
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03749 seconds