|
|
|
Re: Issues with SWT 3.5 and Solaris (Sparc) [message #546012 is a reply to message #546011] |
Fri, 09 July 2010 21:25 |
Jay Mising name Messages: 11 Registered: July 2010 |
Junior Member |
|
|
Sorry, here is the full line of code it is crashing on:
shell.setImages(new Image[] {
new Image(display, clazz.getResourceAsStream("resource/DJIcon16x16.png")),
new Image(display, clazz.getResourceAsStream("resource/DJIcon24x24.png")),
new Image(display, clazz.getResourceAsStream("resource/DJIcon32x32.png")),
new Image(display, clazz.getResourceAsStream("resource/DJIcon48x48.png")),
new Image(display, clazz.getResourceAsStream("resource/DJIcon256x256.png")),
});
With error:
The program 'SWT' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 316 error_code 16 request_code 18 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.)
|
|
|
Re: Issues with SWT 3.5 and Solaris (Sparc) [message #546595 is a reply to message #546012] |
Tue, 13 July 2010 13:53 |
Grant Gayed Messages: 2150 Registered: July 2009 |
Senior Member |
|
|
Hi,
If the app you're running requires use of the Browser then the solaris-motif
build will not work because it does not have Browser support.
The error you're seeing on solaris-gtk seems unrelated to the Browser. Are
you physically sitting at the Solaris machine, or are you remoting to it
from elsewhere? I've encountered X Window System errors when remoting from
an older X environment to a newer one as a result of incompatibilities
between the two. If you see this problem while sitting at the Solaris
machine then please log a bug with swt at
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform &component=SWT
and provide steps to reproduce the problem.
Thanks,
Grant
"Jay" <jmandawg@hotmail.com> wrote in message
news:i1844h$mib$1@build.eclipse.org...
> Sorry, here is the full line of code it is crashing on:
>
> shell.setImages(new Image[] {
> new Image(display,
> clazz.getResourceAsStream("resource/DJIcon16x16.png")),
> new Image(display,
> clazz.getResourceAsStream("resource/DJIcon24x24.png")),
> new Image(display,
> clazz.getResourceAsStream("resource/DJIcon32x32.png")),
> new Image(display,
> clazz.getResourceAsStream("resource/DJIcon48x48.png")),
> new Image(display,
> clazz.getResourceAsStream("resource/DJIcon256x256.png")),
> });
>
> With error:
>
>
> The program 'SWT' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadLength (poly request too large or internal Xlib length
> erro'. (Details: serial 316 error_code 16 request_code 18 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.)
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03769 seconds